fix(chrome): provide missing useId container dependency for Sheet component

[jzempel]

Description

While working on a project with Garden dependencies, I realized that react-chrome fails to install in certain environments due to a missing react-uid dependency. This is often masked, since react-notifications pulls it in. Since Garden no longer recommends react-uid in favor of the more stable useId from @zendeskgarden/container-utilities, I updated the missing dependency and code accordingly (eventually, we'll also replace uid in notifications useToast).

Checklist

• 👌 design updates will be Garden Designer approved (add the designer as a reviewer)
• 🌐 demo is up-to-date (npm start)
• ⬅️ renders as expected with reversed (RTL) direction
• ⚫ renders as expected in dark mode
• 🤘 renders as expected with Bedrock CSS (?bedrock)
• 💂‍♂️ includes new unit tests. Maintain existing coverage (always >= 96%)
• ♿ tested for WCAG 2.1 AA accessibility compliance
• 📝 tested in Chrome, Firefox, Safari, and Edge

[jzempel]

Even though it is a repeat from the extends, Garden documents id when there are meaningful relationships that result when provided by the consumer (compare PaneProvider).

[coveralls]

coverage: 95.656% (-0.001%) from 95.657%
when pulling 719f613 on jzempel/chrome-dependencies
into 2c2c590 on main.

[ze-flo]

Nice catch! 💯