fix: use correct import attributes syntax

[kanadgupta]

🚥 Resolves #950

🧰 Changes

_{(PR description stolen from readmeio/rdme#993)}

TC39 updated their import assertions to be import attributes and it's a bit of a mess now that we're running tests against Node v22.

Here's what importing JSON in ESM used to look like:

import { x } from "./mod" assert { type: "json" }

now it looks like this:

import { x } from "./mod" with { type: "json" };

Support for this new with keyword was added in Node v18.20.0 and Node v20.10.0 (and is supported on all v21 and v22 channels), but importantly the older assert keyword is not supported in Node v22, so unfortunately our package.json#engines.node field is going to look a little ridiculous for the time being.

Details: https://github.com/tc39/proposal-import-attributes?tab=readme-ov-file#history

🧬 QA & Testing

Annoyingly, we don't have anything in our unit tests to catch this sort of thing at the moment because we have stuff like this:

api/packages/api/src/codegen/languages/typescript/index.ts

Lines 127 to 130 in 353cd8b

	process.env.NODE_ENV === 'test'
	? // eslint-disable-next-line unicorn/prefer-module
	`file:${path.relative(__dirname, path.dirname(require.resolve('@readme/api-core/package.json')))}`
	: `^${corePkg.version}`,

but I confirmed that Node v22 works again with this change. See the before:

And the after: