feat(StaticNotification): initial component functionality

[tay1orjones]

Closes #15697

Based on conversations with @finken2 in #15319 and a few meetings later about blockers faced by their team, and consulting with IBMa - this introduces a new notification component with specific guidance outlined in storybook.

We'll test this with users before adding tests, marking stable, etc.

Changelog

New

• Added experimental unstable__StaticNotification

Testing / Reviewing

• Ensure the warning only pops when it should, and doesn't when it shouldn't

[netlify]

✅ Deploy Preview for v11-carbon-react ready!

Name	Link
🔨 Latest commit	ebaf6e3
🔍 Latest deploy log	https://app.netlify.com/sites/v11-carbon-react/deploys/65c148f544b93f00087765e4
😎 Deploy Preview	https://deploy-preview-15532--v11-carbon-react.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[guidari]

@tay1orjones Locally I can see the warning in the pop-the-warning variant:
Error: interactive child node(s) should have an aria-describedby property with a value matching the value of titleId.

But if you check the deploy both variants looks the same. The experimental-unstable-staticnotification--with-interactive-elements-that-pop-the-warning is not poping the warning like is happening locally.

Maybe when we deploy for real it might fix? 🤔 Let's keep an eye on it

[guidari]

LGTM! 🚀
We just have to update the snapshot to fix the test error. For some reason I can't push a commit here

[tay1orjones]

@guidari Yes this is actually intentional, the warning is guarded behind __DEV__ which is only true in non-production environments. So the warning will never pop in production, but will be present in development environments where it can be appropriately addressed by devs.

I'll see if I can get that snapshot updated to pass the ci check