feat: Adding new i18n strings for date-range-picker in preparation for month granularity

[dpitcock]

Adding new i18n strings to the date-range picker in preparation for month granularity

• New strings and english message submitted in CR-173719099, CR-165479809
• Translations completed
• result has been build, copied and and committed to this package

Related links, issue #, if available: n/a

How has this been tested?

all tests ran to confirm no failures, especially confirming no updates to snapshots have been applied

Review checklist

The following items are to be evaluated by the author(s) and the reviewer(s).

Correctness

• Changes include appropriate documentation updates.
• Changes are backward-compatible if not indicated, see CONTRIBUTING.md.
• Changes do not include unsupported browser features, see CONTRIBUTING.md.
• Changes were manually tested for accessibility, see accessibility guidelines.

Security

• If the code handles URLs: all URLs are validated through the checkSafeUrl function.

Testing

• Changes are covered with new/existing unit tests?
• Changes are covered with new/existing integration tests?

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.45%. Comparing base (708ecb7) to head (69ac6d0).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3228   +/-   ##
=======================================
  Coverage   96.45%   96.45%           
=======================================
  Files         791      791           
  Lines       22315    22315           
  Branches     7667     7659    -8     
=======================================
  Hits        21524    21524           
  Misses        739      739           
  Partials       52       52           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[dpitcock]

No longer necessary as a merge conflict is demanding another revision to the PR, so including the changes there