As a registry-tool/registry-user I want to ensure leading multiple forward-slashes in request paths are stripped out

[jimmie]

🧑‍🔬 User Persona(s)

Some tools insert and extra forward slash between base registry URL (pds.nasa.gov/api/search/) and the command path (/bundles/).

💪 Motivation

This causes a 503 from the service which does not recognize the request which arrives w/ these multiple slashes (//bundles/) but should be tolerated.

📖 Additional Details

This can be handled at the Cloudfront layer

⚖️ Acceptance Criteria

Given a registry request URL; https://pds.nasa.gov/api/search/1.0/bundles/urn:nasa:pds:duxbury_pdart14_mariner69::2.0
When I submit this URL either in a browser or via curl
Then I expect the request to return a 200 and valid results, not a 503 response

⚙️ Engineering Details

Have the cloudfront function detect if multiple leading slashes exist and replace them with one.

[jimmie]

PR 209 reviewed and merged.

[miguelp1986]

Test results: https://cae-testrail.jpl.nasa.gov/testrail/index.php?/tests/view/4133328