[Copay Errors] Go through config for VBS and get values mapped properly

[digitaldrk]

Issue Description

Given: We want VBS to remain stable throughout platform changes
When: VSP makes changes to our infrastructure
Then: Our system will not fall apart

Fresh off a week of down-age with VBS, it's come to my attention that our configuration across the following repos and services is brittle.

vets-api -> vsp-infra-application-manifests -> AWS parameter store

Prod uses a vbs_v2 namespace, qa does not. QA was using a host parameter store to declare the host env var value, Prod was using the url parameter store value to declare the host env var.

Tasks

• Maybe start at the manifest level. Look into what is mapping to the env variables we are setting, make necessary changes
• Make sure what we change in the manifest actually exists in parameter store and the value in parameter store is valid
• Do all of the above in both Staging and Prod start in Staging

Design and Front End sync on implementation of design

• Required
• Complete
• Not Required

Acceptance Criteria

• Staging and Prod have documented mappings for all VBS config values
• PR's for Staging are submitted
• We can follow up with Prod PRs when we feel brave, Prod is working currently

Testing

• N/A if non development work
• Testing passed and documented in this ticket based off the "Then" statement in the description

Test procedures:
If additional testing steps or credentials to perform testing are needed list them here

Ticket Creation - Definition of Ready

Ticket requirements

• Description written
• Tasks defined
• Acceptance criteria written
• Testing defined
• Add Labels
• Assign Type
• Assign Priority (Normal = Medium)
• Assign Group(s)
• Assign to a Project
• Attach to an Parent Epic
• Estimate Points