[Linting] Eslint v9 dependency upgrades

[KenAJoh]

Description

Looked up all our eslint-packages and checked their compat with Eslint v9.
Besides eslint-plugin-storybook and eslint-plugin-testing-library it looks like every other package now supports it. Could consider removing eslint-plugin-testing-library if @vitest/eslint-plugin handles most of it anyways

useDescendant update

Because of this change i had to update the component-names
facebook/react#25162

Component Checklist 📝

• JSDoc
• Examples
• Documentation
• Storybook
• Style mappings (@navikt/core/css/config/_mappings.js)
• Component tokens (@navikt/core/css/tokens.json)
• CSS class deprecations (@navikt/aksel-stylelint/src/deprecations.ts)
• Exports (@navikt/core/react/src/index.ts and @navikt/core/react/package.json)
• New component? CSS import (@navikt/core/css/index.css)
• Breaking change? Update migration guide. Consider codemod.
• Changeset (Format: <Component>: <gitmoji?> <Text>. E.g. "Button: ✨ Add feature xyz.")

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8ca1225

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Storybook demo

082663c03 | 91 komponenter | 144 stories

[HalvorHaugan]

I think we can live without eslint-plugin-storybook, at least temporarily.