refactor: [M3-6708] – Implement new React 18 hooks

[dwiley-akamai]

Description 📝

With our recent upgrade to React 18, we can begin making use of new hooks that were introduced with that version. This PR implements useId() in a few files.

• useId
  • One potential use case we discussed early on was using this hook for generating unique IDs for React list items, but the docs explicitly state this should not be done. Of the scenarios outlined in the "Usage" section of the docs, the most relevant one for us is generating unique IDs for accessibility attributes.
• useTransition
  • Our use of React Query and reliance on the loading state it provides makes useTransition mostly superfluous to us.
• useDeferredValue
  • May have some applicability, but it cannot be used as a 1:1 replacement everywhere we do debouncing. For example, we often debounce to limit API requests.
• useInsertionEffect
  • Seems it can be a replacement for componentDidMount and componentWillUnmount, so it may have some applicability when converting class components to function components.

Changes 🔄

• Update Coding Standards doc
• Implement useId() in GroupByTagToggle.tsx, LinodeConfigDialog.tsx, DisplayGroupedLinodes.tsx, DisplayLinodes.tsx, and SortableTableHead.tsx

How to test 🧪

Verification steps

With VoiceOver on, ensure there have been no regressions/changes compared to prod for the following:

1. Linode Config Dialog -- Virt Mode section
2. Linode landing page -- Summary/List view button, Group by Tag button

Alternatively or in addition to the above, you can verify by looking at the HTML and confirming that the id and aria-describedby attributes on the related elements match up:

As an Author I have considered 🤔

• 👀 Doing a self review
• ❔ Our contribution guidelines
• 🤏 Splitting feature into small PRs
• ➕ Adding a changeset
• 🧪 Providing/Improving test coverage
• 🔐 Removing all sensitive information from the code and PR description
• 🚩 Using a feature flag to protect the release
• 👣 Providing comprehensive reproduction steps
• 📑 Providing or updating our documentation
• 🕛 Scheduling a pair reviewing session
• 📱 Providing mobile support
• ♿ Providing accessibility support

[dwiley-akamai]

We moved away from this convention about a year ago, but this was lingering in our Coding Standards.

[dwiley-akamai]

If/when other newly-introduced hooks get used in the code base, perhaps guidelines/explanations around their usage could be included in this section also.

[abailly-akamai]

This makes sense, and achieves the intended result - ✅

thanks for updating the documentation!