feat(project): add flat exports for namespaced components

[tay1orjones]

Closes #8901

Adds new flat exports for previously namespaced components, like PasswordInput, deprecating (with notices) the old TextInput.PasswordInput

Changelog

New

• added flat exports for PasswordInput, ControlledPasswordInput, and FilterableMultiSelect
• added new deprecateFieldOnObject() and deprecation notices for the old exports
• added a migration doc too

Testing / Reviewing

• Public API snapshot should now include these new exports at the root level in addition to retaining the old namespaced exports
• I modified the import path of the TextInput in the TextInput story file, so if you go to that story locally and view the PasswordInput stories, you'll see the console warning pop:
  

[netlify]

✔️ Deploy Preview for carbon-react-next ready!

🔨 Explore the source changes: b8df84e

🔍 Inspect the deploy log: https://app.netlify.com/sites/carbon-react-next/deploys/60fb14e52ac8550008bbfb05

😎 Browse the preview: https://deploy-preview-9008--carbon-react-next.netlify.app

[netlify]

✔️ Deploy Preview for carbon-elements ready!

🔨 Explore the source changes: b8df84e

🔍 Inspect the deploy log: https://app.netlify.com/sites/carbon-elements/deploys/60fb14e50c3341000753d923

😎 Browse the preview: https://deploy-preview-9008--carbon-elements.netlify.app

[netlify]

✔️ Deploy Preview for carbon-components-react ready!
Built without sensitive environment variables

🔨 Explore the source changes: b8df84e

🔍 Inspect the deploy log: https://app.netlify.com/sites/carbon-components-react/deploys/60fb14e51cf5a50007c3ead3

😎 Browse the preview: https://deploy-preview-9008--carbon-components-react.netlify.app

[tay1orjones]

This is ready for review, but I'm unsure how best to fix the tests. The public api snap updates, but the test fails because the components are calling console.warn().

I don't think we want to jest.spyOn(global.console, "warn").mockImplementation(() => {}) because that would swallow all warnings. Conditionally swallowing only console.warn for the listed components of this PR would still swallow things we'd want caught. I'm not sure what the best approach is to fix this 🤔 Any suggestions?

[tw15egan]

@tay1orjones is there any way to check for a specific warning message? Or a snippet from the message like "Please import and use" so that it will catch all of our deprecation warnings, but still emit the rest?

[tay1orjones]

@tw15egan thanks for the idea! I pushed an update to do just that, it matches on the "field has been deprecated" substring.

[tw15egan]

LGTM 👍 ✅

[joshblack]

Looking great 🔥 Just left a note about the mock strategy that can help out with tests and I think after that should be good to go 🚢

[tay1orjones]

Very much appreciate the suggestions @joshblack - all have been addressed. The mock approach feels much cleaner ✨ 👍