Allow to toggle between package.json support + further cleanups from the gi.ts merge

[JumpLink]

• Renamed CLI argument packageYarn to workspace as other package managers such as PNPM also support this protocol
• Ambient module definitions are now always generated with and without versions prefix (previously this was only the case for the latest versions). I think this makes sense, as care should be taken not to use the same library in different versions anyway. If this is needed anyway, it can be prevented with the new generate option onlyVersionPrefix. This fixes Allow all versions to be imported without a version string (e.g. gi://Gtk instead of gi://Gtk?version=4.0) in #158 and possibly #174
• A index.d.ts file are now created for each module with which everything for the module (ambient module, imports.gi and namespace) can be imported
• Synchronous methods removed that existed twice for the asynchronous variant, this was originally criticised in #162
• Support for type generation without package.json support to fix #168 and #173, for this there is a new cli agrument package to be able to toggle between package.json support. package.json support is disabled by default.

[ewlsh]

Taking a look...

[JumpLink]

@ewlsh Some in the GNOME community want the types to work without package.json and NPM.

I think for types without package.json support it is easier to generate all gir types in a single file, because in Ambient modules no relative imports are allowed and without package.json support only relative imports are possible. I will try that next.