Encode the datetime values in the bundle.Link.URL in the resource

[sagarsarvankar]

Describe the bug
When there are many records for a resource, it gives "next" url in the bundle. We have a case as below
"link": [
{
"relation": "self",
"url": "https://fhirserver.justtest.in:9443/fhir-server/api/v4/Observation?_count=10&category=vital-signs&date=gt1940-10-04T00:00:00+00:00&patient=17e77411359-8837d878-ea1e-45b5-bb89-882fdfb2be4b&_page=1"
},
{
"relation": "next",
"url": "https://fhirserver.justtest.in:9443/fhir-server/api/v4/Observation?_count=10&category=vital-signs&date=gt1940-10-04T00:00:00+00:00&patient=17e77411359-8837d878-ea1e-45b5-bb89-882fdfb2be4b&_page=2"
}
Here in the URL, there is "+" sign in the date parameter, and hence the GET on this URL to FHIR server fails saying below
{
"resourceType": "OperationOutcome",
"id": "ac-1f-5-a3-1d80ad82-06d4-41c1-9f6a-2cd2c2ecfc7a",
"issue": [
{
"severity": "fatal",
"code": "invalid",
"details": {
"text": "Invalid Date Time Format found please use 'yyyy-mm-ddThh:mm:ss[Z|(+|-)hh:mm].'"
},}]}

Environment
4.10.1

To Reproduce
Steps to reproduce the behavior:

1. search with a timestamp that include timezone offset
2. check the self url

Expected behavior
The returned URL after encoding should look like https://fhirserver.justtest.in:9443/fhir-server/api/v4/Observation?_count=10&category=vital-signs&date=gt1940-10-04T00:00:00%2B00:00&patient=17e77411359-8837d878-ea1e-45b5-bb89-882fdfb2be4b&_page=2
where + is replaced with %2B

More details are located at https://www.hl7.org/fhir/http.html#paging it says "The links are opaque to the client, have no dictated structure, and only the server understands them. The client must use the server supplied links in order to traverse the pages."

Also, there was a discussion in the chat and is available at https://chat.fhir.org/#narrow/stream/212434-ibm/topic/Bundle.20Link.20URL

[tbieste]

I verified that each '+' in the link URLs are encoded as %2B.