Support import-attributes and deprecate import-assertions

[IWANABETHATGUY]

Recently, Typescript introduced a new syntax https://devblogs.microsoft.com/typescript/announcing-typescript-5-3/#import-attributes, and deprecated the old import-assertions, maybe we should follow.

Reference

• proposal: https://github.com/tc39/proposal-import-attributes
• implementation: feat(53656): Add support for the updated import attributes proposal microsoft/TypeScript#54242

[magic-akari]

• feat(ast): implement new proposal-import-attributes #1476

[IWANABETHATGUY]

• feat(ast): implement new proposal-import-attributes #1476

Sorry, I didn't notice that, also maybe we should deprecate the import-assertions rather than replace them directly, just like Typescript did?

[magic-akari]

• feat(ast): implement new proposal-import-attributes #1476

Sorry, I didn't notice that, also maybe we should deprecate the import-assertions rather than replace them directly, just like Typescript did?

This PR adds support for with and assert in the parse and codegen stages, including Formatter. Both of them are supported without deprecation or replacing the support for the previous syntax.
Perhaps we can consider adding assert checks during the linting stage.

[IWANABETHATGUY]

• feat(ast): implement new proposal-import-attributes #1476

Sorry, I didn't notice that, also maybe we should deprecate the import-assertions rather than replace them directly, just like Typescript did?

This PR adds support for with and assert in the parse and codegen stages, including Formatter. Both of them are supported without deprecation or replacing the support for the previous syntax. Perhaps we can consider adding assert checks during the linting stage.

LGTM