Authors to assign component's label

[anasalkouz]

Is your feature request related to a problem? Please describe.
Coming from this. We need to reduce the time and effort to assign component's label (as we broke it down here) to newly created issues.

Describe the solution you'd like
We need to update the "feature request" and "bug report" templates to include a required dropdown menu that include all component's labels as defined here. Author has the most context regarding the reported bug or the feature request and most probably they will know the related component. Author need to assign at least one value from the dropdown menu, then we need to run a action which will tag the issue with the corresponding github label.

We should ensure the process doesn't dissuade anyone from creating a new issue, may be we need to provide a description before the dropdown menu, tilling people if you are not fully sure which component to pick, do your best guess and maintainers can fix it later on if needed. In addition, I think we should keep the option for authors to select a generic value if they are really don't know, such as "Other" or "I don't know".

Additional context
Using forms in github: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms

[Pallavi-AWS]

Assigning the component labels at the time of opening issues will give a good starting point for the component teams to triage issues. The issue can always be moved to a downstream/another component on initial analysis by the first component. This will help us scale and avoid the buildup of untriaged issues.

[Pallavi-AWS]

@mch2 requesting your help in getting the issue template changed in order to assign component labels. Thanks.