feat: Changed the 1password secret reference for secret that switched vault

Closes https://github.com/MobilityData/product-tasks/issues/89

Summary:

Changed the secret reference path for the 1 password API Key — API_SOURCE_SECRETS secret, since it was moved to a different vault (from TECH: Keys & Tokens to TECH: Feeds Keys & Tokens) Currently only a copy was done (not a move). The original secret should be removed from the TECH: Keys & Tokens once the change as been proven as working.

Expected behavior:

The contractor is able to add data to the API Key — API_SOURCE_SECRETS secret in the new vault. The batch processing is able to download the dataset from the authenticated feed.

Testing tips:

Go to the GCP secret manager (requires authorization)
Take a note of the version of the FEEDS_CREDENTIALS.
Run db-update-qa.yml
Go back to GCP secret manager. The version should be one more than what you noted.

Please make sure these boxes are checked before submitting your pull request - thanks!

[ ] Run the unit tests with ./scripts/api-tests.sh to make sure you didn't break anything
[ ] Add or update any needed documentation to the repo
[x] Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
[x] Linked all relevant issues
[ ] Include screenshot(s) showing how this pull request works and fixes the issue(s)

MobilityData / mobility-feed-api

feat: Changed the 1password secret reference for secret that switched vault #709