Build tool's plugin options

Nessuno ha ancora preso questa issue.

There are several reasoning to be done around "how we expect" users to use Kiota in their projects, among others:
- generate sources and commit the generated result
- have some sort of script to automate the code generation

Personally, I do like the approach that considers a codegen tool 100% idempotent and the generated code should be reproducible and not committed in the versioning system (i.e. regenerated all the time, build tools are good at caching the results on dev machines).

Following this(opinionated) philosophy I started automating the code generation wrapping the `kiota` CLI in a Maven plugin:
https://github.com/andreaTP/kiota-utils/blob/main/plugin/src/main/java/io/apicurio/kiota/KiotaMojo.java

Here I'm asking if you have already considered this aspect and what your take on the subject is.
More specifically, would you accept Maven/Gradle plugins in this repo or you prefer them to be third-party?

Inizia leggendo l’issue e riesaminando l’implementazione collegata del plugin Maven KiotaMojo.java. Confronta gli approcci proposti per i plugin Maven e Gradle con l’attuale workflow di generazione del codice del repository. Il lavoro non è ancora definito oltre la decisione se tali plugin debbano appartenere a questo repository o rimanere plugin di terze parti.

Scritto dal modello di indicizzazione a partire dal testo della issue.