[chore] add githubgen tool to enhance issue templates

[mowies]

This PR enhances some of the existing issue templates by changing them to be interactive forms, similar to collector-contrib. This is needed to be able to automate codeowner updates and to then be able to ping codeowners reliably with automated tooling.

Follow ups:

• move the githubgen tool to a central place so that we don't need to duplicate it in contrib and core repos

Part of #11562

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.44%. Comparing base (5272797) to head (3b7fa2d).
Report is 96 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #11756   +/-   ##
=======================================
  Coverage   91.44%   91.44%           
=======================================
  Files         446      446           
  Lines       23742    23742           
=======================================
  Hits        21712    21712           
  Misses       1654     1654           
  Partials      376      376           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mowies]

removed since some is an actual user and not affiliated or related to OTel

[mowies]

hope this fine since @atoulme is also maintainer for the tool in contrib :)

[atoulme]

feel free to put your name here too.

[mowies]

i added this for completeness sake and to make githubgen work correctly. owners list taken from current codeowners file

[evan-bradley]

Follow ups: move the githubgen tool to a central place so that we don't need to duplicate it in contrib and core repos

https://github.com/open-telemetry/opentelemetry-go-build-tools/ is probably the right place. Could we just pull the module from contrib (like we do with chloggen) and if we move it update the reference? Referencing it in the internal/tools package should be fairly straightforward.

[mowies]

@evan-bradley that would be possible but I made a few minor changes to the tool to make it work with this repo (e.g. changing the file templates), so that would need to be parameterized in the original tool first to be able to do that. I wanted to do exactly that in a follow up issue afterwards to be able to clearly see what we need to change in the tool to make it general enough to serve both or even more repos in the future.

[mowies]

I filed open-telemetry/opentelemetry-collector-contrib#36691 to take care of moving githubgen to the build-tools repo

[atoulme]

yes, go-build-tools seems like a better home.

[mx-psi]

@mowies Do you think moving to go-build-tools as a first step is doable? I think it's probably less of a hassle than copying the code here

[mowies]

I'm already working on it :)
Draft PR is open, but that will take a little bit cus the tool has 0 unit tests

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[mowies]

this is still active

[atoulme]

Looking good to me, how about getting it out of draft and fixing conflicts, and then we can get it in?

[mowies]

yes! but ideally, i'd like to merge and maybe also release open-telemetry/opentelemetry-go-build-tools#655 first