feat: Deprecation Warning when Creating a Legacy Library

[kdmccormick]

Description

Adds this warning banner:

Supporting information

Part of: #2876

Merge considerations

• Needs Product/UX review before merging

Testing instructions

N/A

Best Practices Checklist

We're trying to move away from some deprecated patterns in this codebase. Please
check if your PR meets these recommendations before asking for a review:

• Any new files are using TypeScript (.ts, .tsx).
• Deprecated propTypes, defaultProps, and injectIntl patterns are not used in any new or modified code.
• Tests should use the helpers in src/testUtils.tsx (specifically initializeMocks)
• Do not add new fields to the Redux state/store. Use React Context to share state among multiple components.
• Use React Query to load data from REST APIs. See any apiHooks.ts in this repo for examples.
• All new i18n messages in messages.ts files have a description for translators to use.
• Imports avoid using ../. To import from parent folders, use @src, e.g. import { initializeMocks } from '@src/testUtils'; instead of from '../../../../testUtils'

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.74%. Comparing base (106f22b) to head (935f2ec).
⚠️ Report is 147 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff            @@
##           master    #2563    +/-   ##
========================================
  Coverage   94.74%   94.74%            
========================================
  Files        1218     1218            
  Lines       27312    27313     +1     
  Branches     5988     6147   +159     
========================================
+ Hits        25878    25879     +1     
+ Misses       1376     1363    -13     
- Partials       58       71    +13     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jmakowski1123]

Thanks for the catch Kyle. I'm fine with the banner approach, given this is a temporary warning.

1. I feel confident enough to say the "new" libraries will be out of Beta by Verawood. If we have similar confidence in the deprecation/migration timeline, we could specify Verawood instead of "future release". I don't see any red flags on that in terms of the migrations.
2. Let's link to the new libraries Studio tab.

[rpenido]

Hi @kdmccormick! I started working on #2876.
Do you want me to check the CI error here so this PR can be merged?
Thanks!

[kdmccormick]

Yes please @rpenido !

We were also hoping that this warning would link to the V2 libraries interface, and wouldn't say "Libraries (Beta)".