Build tool's plugin options

Nobody has claimed this yet.

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?

Start by reading the issue and reviewing the linked KiotaMojo.java Maven plugin implementation. Compare the proposed Maven and Gradle plugin approaches with the repository's current code-generation workflow. The work is not yet defined beyond deciding whether such plugins belong in this repository or should remain third-party.

Written by the indexing model from the issue text.