Issue templates

[laysabit]

PR Checklist

PR Structure

• This PR has reasonably narrow scope (if not, break it down into smaller PRs).
• This PR avoids mixing refactoring changes with feature changes (split into two PRs
  otherwise).

Thoroughness

• This PR adds tests for the most critical parts of the new functionality or fixes.
• I've updated the docs and README with the added features, breaking changes, new instructions on how to use the repository.

Release planning

• I've decided if this PR requires a new major/minor/patch version accordingly to
  semver, and I've changed the name of the BRANCH to release/* , feature/* or patch/* .

What

New folder in .github with:

• bug_report.md
• feature_request.md

Why

So we have an organized and patternized issues section.

So the user pick between raising an issue related to a bug or a general enhancement for the repository.

Known limitations

[N/A]