SARAALERT-1599: Update Vaccine Products Names to CDC Formatting

[ngfreiter]

Description

Jira Ticket: SARAALERT-1599

This updates product_name for vaccines to be in compliance with the official CDC product names for the relevant vaccines. We are doing this to minimize any variation in the names of the vaccines.

Important Changes

vaccines.yaml

• Update vaccine names to match CDC guidance

advancedFilterOptions.js

• Update vaccine names to match CDC guidance

db/migrate

• Add a migration for going from the old "new" vaccine product names to the new new vaccine names

public/Sara Alert Import Format.xlsx

• Update guidance, example, and section detailing updates

test/*

• Update all test files to match new vaccine names

Testing Recommendations

• The new values are used in the UI
• The new values are used in import
• The new values are used in the API
• If you migrate from a database using the old values, the values are correctly updated on:
  • Vaccine records
  • UserExportPreset records which use the vaccines in their config
  • UserFilter records which filter based on these product names
• If you migrate back, the reverse happens

Checklists

Submitter:

• This PR describes why these changes were made.
• This PR is into the correct branch.
• This PR includes the correct JIRA ticket reference.
• Comment added to the relevant JIRA ticket(s) with a link to this PR
• Code diff has been reviewed (it does not contain: additional white space, not applicable code changes, debug statements, etc.)
• If UI changes have been made, Chrome Dev Tools Lighthouse accessibility test has been executed to ensure no 508 issues were introduced.
• Tests are included and test edge cases
• Tests have been run locally and pass (remember to update Gemfile when applicable)
• Test fixtures updated and documented as necessary

@Bialogs

• Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
• The tests appropriately test the new code, including edge cases
• You have tried to break the code
• If applicable, you have tested changes against a large database, and considered possible performance regressions
• Tested all recommendations listed in the "Testing Recommendations" section. The application behaves as expected with this PR.

@tstrass

• Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
• The tests appropriately test the new code, including edge cases
• You have tried to break the code
• If applicable, you have tested changes against a large database, and considered possible performance regressions
• Tested all recommendations listed in the "Testing Recommendations" section. The application behaves as expected with this PR.

@sgober

• Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
• The tests appropriately test the new code, including edge cases
• You have tried to break the code
• If applicable, you have tested changes against a large database, and considered possible performance regressions
• Tested all recommendations listed in the "Testing Recommendations" section. The application behaves as expected with this PR.