fix: suppress warnings from useId imports and prop usage

[booc0mtaco]

Summary:

• move the console.warn inside the function usage (TODO: consider deduping its output)
• use proper camelCase prop name in textarea tests

Test Plan:

• Wrote automated tests
• CI tests / new tests are not applicable
• Manually tested my changes, but I want to keep the details secret
• Manually tested my changes, and here are the details:
  • Create an alpha publish and try out in edu-stack or traject as a sanity check if changes affect build or deploy, or are breaking, such as token changes, widely used component updates, hooks changes, and major dependency upgrades.

[github-actions]

size-limit report 📦

Path	Size
components	94.5 KB (+0.03% 🔺)
styles	36.61 KB (0%)

[codecov]

Codecov Report

Merging #1606 (70a2dbe) into next (4d32194) will decrease coverage by 0.07%.
The diff coverage is 25.00%.

@@            Coverage Diff             @@
##             next    #1606      +/-   ##
==========================================
- Coverage   91.39%   91.32%   -0.07%     
==========================================
  Files         280      280              
  Lines        4193     4195       +2     
  Branches      787      787              
==========================================
- Hits         3832     3831       -1     
- Misses        335      338       +3     
  Partials       26       26              

Impacted Files	Coverage Δ
...components/TextareaField/TextareaField.stories.tsx	100.00% <ø> (ø)
src/util/useId.ts	38.46% <25.00%> (-16.09%)	⬇️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[ghost]

So this message will potentially be logged a lottt more now? Is that a concern

[ghost]

surprised this wasn't a typescript error before. Would is have been if you changed as Meta<Args> to satisfies Meta<Args>?

[booc0mtaco]

it's possible. I can test that out. It's also possible typescript might allow both, and only warns at runtime... which react does for some kinds of things (the lower-case prop actually does what it says it should)

EDIT: using satisfies works better ! :) it complains when I use the lowercase one. It would be a good tidying task to move all of the tests over to that syntax at some point.. also looks like i lied :( i thought it was applying the prop but it updated the snapshots this time along with the chromatic snaphots

[booc0mtaco]

So this message will potentially be logged a lottt more now? Is that a concern

Thinking about the browser case, the messages would collapse under a counted set instead of printing all on separate rows if it printed multiple times. I can add a boolean toggle at the higher scope to print this exactly once, since it could become obnoxious.