Fix metadata 'level' labeling

[marcellamaki]

Summary

Description of the change(s) you made

Adds necessary conditions (due to a mis-match of strings/mapping) to ensure that all string references are able to be translated on the Resource Panel as well as on the display chips

Fixes #3664

Manual verification steps performed

1. Add a resource
2. Add all levels to the resource - ensuring accurate display in the dropdown and in the chips within the form
3. Save and exit. Check the display in the comfortable/default view on the main channel page to ensure chips are displaying strings accurately
4. Open the side panel and ensure that the strings are displaying correctly for all levels there.

Screenshots (if applicable)

Does this introduce any tech-debt items?

This does not add any new tech-debt, but it also doesn't resolve the strings problem, which should probably be revisited. The translation logic in general for all of the metadata work is replicated in a lot of places at this point, and could probably be refactored or otherwise cleaned up.

---

Reviewer guidance

How can a reviewer test these changes?

See manual verification steps above

---

Contributor's Checklist

PR process:

• If this is an important user-facing change, PR or related issue the CHANGELOG label been added to this PR. Note: items with this label will be added to the CHANGELOG at a later time
• If this includes an internal dependency change, a link to the diff is provided
• The docs label has been added if this introduces a change that needs to be updated in the user docs?
• If any Python requirements have changed, the updated requirements.txt files also included in this PR
• Opportunities for using Google Analytics here are noted
• Migrations are safe for a large db

Studio-specifc:

• All user-facing strings are translated properly
• The notranslate class been added to elements that shouldn't be translated by Google Chrome's automatic translation feature (e.g. icons, user-generated text)
• All UI components are LTR and RTL compliant
• Views are organized into pages, components, and layouts directories as described in the docs
• Users' storage used is recalculated properly on any changes to main tree files
• If there new ways this uses user data that needs to be factored into our Privacy Policy, it has been noted.

Testing:

• Code is clean and well-commented
• Contributor has fully tested the PR manually
• If there are any front-end changes, before/after screenshots are included
• Critical user journeys are covered by Gherkin stories
• Any new interactions have been added to the QA Sheet
• Critical and brittle code paths are covered by unit tests

---

Reviewer's Checklist

This section is for reviewers to fill out.

• Automated test coverage is satisfactory
• PR is fully functional
• PR has been tested for accessibility regressions
• External dependency files were updated if necessary (yarn and pip)
• Documentation is updated
• Contributor is in AUTHORS.md

[bjester]

LGTM

[pcenov]

Confirmed as fixed at Hotfixes.