Otherwise TypeScript will raise TS2322 errors. I have no idea why and
how does the fix work. But it does.

Even importing the `ReservedProps` and `NativeElements` types from
`jsx-runtime` instead of declaring them in the module would fail the
tests. I have no idea why, either.

The failing tests are at https://github.com/vuejs/ecosystem-ci/actions/runs/4538928668/jobs/7998297656#step:7:3

Fixes use cases such as https://github.com/vuetifyjs/vuetify/blob/29777628ac8839c0548e869d3d350ed9fdcbb149/packages/vuetify/src/shims.d.ts#L18-L25

Adds a new `./jsx.d.ts` entry in `@vue/runtime-dom` to avoid duplication
in `vue`. It should be removed in 3.4 when we stop registering global
JSX namespace by default.

Drops `vue/jsx-runtime/dom`.
The previous commits didn't work because imported (and re-exported)
types cannot be augmented.
So I give up on the idea of moving the DOM types to `vue/jsx-runtime`.
They don't pollute the global namespace anyway.

There's still one caveat that I have to import the
`IntrinsicElementAttributes` type from
`@vue/runtime-dom/dist/runtime-dom` rather than using the package name
as entry. Seems because in this monorepo, TypeScript always picks up
the source file (`index.ts`) over the built file
(`dist/runtime-dom.d.ts` as specified in the `types` field in
`package.json`)