Introduce issue forms

[anesabml]

What do these changes do?

Introduce the new issue forms

Are there changes in behavior for the user?

No.

Related issue number

No.

Checklist

• [x] I think the code is well written
• [ ] Unit tests for the changes exist
• [ ] Documentation reflects the changes
• [ ] Add a new news fragment into the CHANGES folder
  • name it <issue_id>.<type> (e.g. 588.bugfix)
  • if you don't have an issue_id change it to the pr id after creating the PR
  • ensure type is one of the following:
  • .feature: Signifying a new feature.
  • .bugfix: Signifying a bug fix.
  • .doc: Signifying a documentation improvement.
  • .removal: Signifying a deprecation or removal of public API.
  • .misc: A ticket has been closed, but it is not of interest to users.
  • Make sure to use full sentences with correct case and punctuation, for example: Fix issue with non-ascii contents in doctest text files.

[codecov[bot]]

Codecov Report

Merging #863 (14009c3) into master (76ca15f) will not change coverage. The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #863   +/-   ##
=======================================
  Coverage   93.43%   93.43%           
=======================================
  Files          11       11           
  Lines        1568     1568           
  Branches      186      186           
=======================================
  Hits         1465     1465           
  Misses         72       72           
  Partials       31       31           

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 76ca15f...14009c3. Read the comment docs.

[Pliner]

Thanks