Add new issue templates for backport requests and community issues

[zakkak]

Depends on #9825

cc @jerboaa @simonis @dchuyko

[Karm]

@zakkak \n ?
And an absolute nitpick: We know the rather limited set of versions to reasonably backport to, so how about dropdown ? https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema#about-githubs-form-schema

[zakkak]

I didn't go for a dropdown because:

1. I expect this to be used for Oracle GraalVM backport requests as well (where the version range is not as limited as in upstream
2. I expect this to be used to request backports to branched versions as well while they are still being prepared for release (e.g. 24.2 right now), so we would need to update the dropdown every 6 months.

I will add the \n thanks

[zakkak]

@fniephaus @alina-yur this is a kind reminder

[zakkak]

Hi @fniephaus @alina-yur , could one of you please have a look at this? Thanks

[alina-yur]

@zakkak sorry for the delay. it's all good, I'll get to it tomorrow.

[alina-yur]

Hi @zakkak, so here's the feedback for this PR. Seems like there are two issues to solve, let's do it in the following way.

• 6_backport_request.yml is ok to merge here (oracle/graal);
• for 7_community_bug.yml, we suggest to move it to graalvm/graalvm-community-jdk21u, as this is more specific to community builds. we would also suggest to remove the vendor labels to keep the community repo vendor-neutral.

[zakkak]

for 7_community_bug.yml, we suggest to move it to graalvm/graalvm-community-jdk21u, as this is more specific to community builds.

This seems to go against our initial decision to track all issues in oracle/graal. For that we would need to re-open the issues support in https://github.com/graalvm/graalvm-community-jdk21u. If we do so it would probably make more sense to have the backport requests (concerning that repository) there as well.

we would also suggest to remove the vendor labels to keep the community repo vendor-neutral.

I see how the dropdown might seem limiting, but I believe we will need some info regarding the build. I suggest keeping the field but making it a text field instead of a dropdown. WDYT?