$r5.apply should generate Bundle.entry.fullUrl and references should be updated to use those fulUrl entires for resolution

[rdingwell]

The following is contained in the specification wrt resolving references in a bundle: Several portions of this algorithm are dependent on on the presence of Bundle.entry.fullUrl. In instances where references might be resolved within a Bundle but entries do not have fullURLs, resolution expectations are undefined.

Currently, the $r5.apply operation produces a bundle with entries that do not have fullUrl attributes. There are also references between the resources contained in the resulting bundle, an example of which is contained below. These references are based solely off of the id of a resources within the Bundle.entry list. This places the resolution of these references outside of a mechanism defined in the specification which can result in errors between implementations that make use of the output of the operation. Adding fullUrl attributes to each of the Bundle.entry items and using references that point to those items would create Bundles that have a specification defined means of resolving references.

 "resource": {
         "reference": "ENACT-1-ACT-1"
  }

[JPercival]

We'll need to add a configuration for the baseUrl as part of the Bundle generation. Currently, this library lives independently of any server and doesn't have any concept of a base server address, so it's up the application consuming this library to rewrite links as needed. The same is true for the next and prev links in the Bundle