POC: codegen from plugin.json

[hugohaggmark]

What this PR does / why we need it:
Initial POC that illustrates how we could generate Typescript files from the plugin.json file.

Kapture.2025-02-21.at.08.27.36.mp4

• The code generation should be made more extendable but I left that part out for now.
• Naming and placement of the files is something we should discuss if moving forward with this solution
• This could be extended to enforce rules in the plugin.json, for example For data source plugins, if the plugin supports alerting. Requires backend to be set to true. Those types of rules could be added here
• Need to add the code generation to the webpack build pipeline too
• Do I dare to mention this could be made for backend go files as well if any of the props in plugin.json have immediate impact on the backend that is

Which issue(s) this PR fixes:

Fixes #grafana/grafana#100898

Special notes for your reviewer:

[github-actions]

Hello! 👋 This repository uses Auto for releasing packages using PR labels.

✨ This PR can be merged. It will not be considered when calculating future versions of the npm packages and will not appear in the changelogs.

[leventebalogh]

Nice one @hugohaggmark, this looks like a good direction to me! 🚀

I guess one of the main benefits of an auto-generated type file for these metadata would be the following: (over just importing the plugin.json, which is what plugins are usually doing now)

• easier to discover available properties without looking at the JSON
• better type safety during development (now the code actually "knows" what includes are available)

Obviously not part of the POC, but if we take this further we could probably somehow "generalise" the generation methods, so it's easy to introduce a new type?

[hugohaggmark]

One thing that I haven't added to this POC yet is that we need to run the code generation before we build too, otherwise the build could potentially break if someone was using the code generated classes/functions/enums.

[tolzhabayev]

@hugohaggmark closing due to #1770

my bad, has nothing to do with the generation of the generic schema docs