Improve the GitHub issues/prs templates

[nolar]

What do these changes do?

Based on the experience of the past 9 months, improve the issue/pr templates by adding the guiding questions and the structure (e.g. in the Bug Reports).

Description

The original templates were taken from the Zalando's template repo and did not use the GitHub's new features.

Now, the new GitHub features will be used:

• Multiple templates for issues: Bug Report, Feature Request, Question, and Security Report.
• The Bug Report contains placeholders for a code snippet and log output, formatted to fold/unfold the long sections.
• All the templates contain the guiding questions for the reporter, to make the issues more complete and detailed. (As comments, so they are visible in the form, but not rendered in the resulting issue/pr.)

The code is not affected in any way. Just the GitHub interaction.

Issues/PRs

Issues: #12 #3

Type of changes

• Mostly CI/CD automation, contribution experience

Checklist

• The code addresses only the mentioned problem, and this problem only
• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes
• If you provide code modification, please add yourself to CONTRIBUTORS.txt

[zincr]

🤖 zincr found 0 problems , 0 warnings

✅ Large Commits
✅ Approvals
✅ Specification
✅ Dependency Licensing

[zincr]

🤖 zincr found 1 problem , 0 warnings

❌ Approvals
✅ Large Commits
✅ Specification
✅ Dependency Licensing

Details on how to resolve are provided below

---

Approvals

All proposed changes must be reviewed by project maintainers before they can be merged

Not enough people have approved this pull request - please ensure that 1 additional user, who have not contributed to this pull request approve the changes.

• ✅ Approved by PR author @nolar
• ❌ 1 additional approval needed
   

[samurang87]

"modifications"

[samurang87]

I could use this line for myself lol