This PR contains:

• bugfix
• feature
• refactor
• documentation
• other

Are tests included?

• yes (bugfixes and features will not be merged without tests)
• no

Breaking Changes?

• yes (breaking changes will not be merged unless absolutely necessary)
• no

List any relevant issue numbers:

Description

This changes how the converters from SWC AST to binary and from binary to JavaScript AST work. Previously, all of them were hand-crafted, which means it was extremely important that every single node was properly checked, all indices aligned and all fields were converted in the right way and order.
To make this easier, the JavaScript converter is now fully generated from a script that reads a config file and automatically assigns indices and orders fields. It also generates constants for the Rust code so that field order is aligned.

To have the same level of efficiency, field types in Rust can contain an "_INLINED_FIELDNAME" suffix which indicates if there is a field that is not referenced via its position but is rather directly added to a node as the last field. In that case, this field needs to be converted first. If the inlined field changes, the type name changes, which ensures we know that the Rust code needs to be updated.

The bigger picture here, though, is that we eventually want to

• Consume the Buffer directly in the Rollup AST classes. To do that, we can now use the same script to generate constants and single property converters as needed.
• Be able to convert an existing JavaScript AST to binary. Again, we can now use the same config file. This is important to handle the case where a plugin returns a JavaScript AST, though we need to think how to handle the case where the plugin adds non-standard properties and nodes.