CHI-3368: Add more translation templates for values that come from config

[stephenhand]

Description

• Categories and Subcategory names can now be translation keys
• Resource filter options can now be translation keys
• Non data call types can now be translation keys

Checklist

• Corresponding issue has been opened
• [n/a] New tests added
• Feature flags added
• Strings are localized
• Tested for chat contacts
• Tested for call contacts

Other Related Issues

None

Verification steps

• Add a translation key to the fr.json file matching a Subcategory name, a Category name, a resource filter option and a non data call type for the helpline
• Load up the UI
• Ensure the English values still appear as normal
• Switch the UI to French
• Refresh
• Confirm the translations are being applied in all 4 places

AFTER YOU MERGE

1. Cut a release tag using the Github workflow. Wait for it to complete and notify in the #aselo-deploys Slack channel.
2. Comment on the ticket with the release tag version AND any additional instructions required to configure an environment to test the changes.
3. Only then move the ticket into the QA column in JIRA

You are responsible for ensuring the above steps are completed. If you move a ticket into QA without advising what version to test, the QA team will assume the latest tag has the changes. If it does not, the following confusion is on you! :-P