chore: Update issue templates

[alexec]

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
• The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
• I've signed the CLA.
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged. N/A
• My builds are green. Try syncing with master if they are not. N/A
• My organization is added to USERS.md.

The goal of this PR is to more quickly capture useful information. Current, IMHO, we ask for too much we don't need and that no one provides. Instead, it would be better to ask for just 1 or 2 key items.