[documentation] #2446: improve issue templates

[6r1d]

Description of the Change

This PR adds detailed forms to fill into the issues. To see the issue form, open this page.

Issue

This PR closes #2446 and covers all the items in it.

Benefits

• Contributors sending the bug requests will fill the form with all the details that are needed for quicker debugging.
• The supported branches of Iroha are immediately visible.
• Contributors also see who to tag, so the issue gets resolved faster.
• People who have questions will immediately see Discord and Telegram community links.

Possible Drawbacks

I have several questions I'll be marking as resolved here.
UPD: these questions were resolved.

• I am not sure where to redirect people who have an SDK problem. In addition to that, it is possible to add a link to SDK in /issues/new/choose. This detail needs to be considered before the merge.
• The Discord server link with #iroha channel shows a Telegram bridge and little activity. Is it the current actual Discord for Iroha?
• The tags are auto-filled and need a change; I have not seen a stable tag, so both types of issues are tagged the same way, making it confusing.
• This PR still has blank_issues_enabled as true for now. I think this will need a bit of a discussion: should we have blank issues in addition to the "bug" issues for questions, not related to bugs or future planning?
• I am not sure if this is the correct documentation link for JSON logs. While all the details match, is it the correct doc to refer to?

Alternate Designs

At a later date, there may be an internal command to collect most of the current Iroha environment data: LibC version, OS info, etc. I am not sure if this can be done reliably all the time, so I am thinking of implementing this at a later date.

[outoftardis]

what about mentioning we have a contributing guide? https://github.com/hyperledger/iroha/blob/iroha2-dev/CONTRIBUTING.md

[outoftardis]

I am not sure if this is the correct documentation link for JSON logs. While all the details match, is it the correct doc to refer to?

I think you want this one: https://github.com/hyperledger/iroha/blob/iroha2-dev/docs/source/references/config.md#logger

[outoftardis]

The Discord server link with #iroha channel shows a Telegram bridge and little activity. Is it the current actual Discord for Iroha?

Iroha channel: https://discord.com/channels/905194001349627914/905205848547155968
But I believe telegram channel is much more active, so I don't know if we even need to provide a link to Discord

[6r1d]

what about mentioning we have a contributing guide? https://github.com/hyperledger/iroha/blob/iroha2-dev/CONTRIBUTING.md

I like that idea, plus it has yet another category we can add besides the bugs:

Note: Issues such as outdated documentation, insufficient documentation, or feature requests should use the Documentation or Enhancement labels. They are not bugs.

In regards to "attaching a screenshot", it's better to update that small part of the doc right after, because we're requesting JSON logs.

[outoftardis]

same comments for the stable bug template

[outoftardis]

a note: please check contributing guidelines, one PR = one commit (we don't squash commits when the pr is merged)

[outoftardis]

please also update the commit message: docs: improve issue templates -> [documentation] #2446: Improve issue templates
and sign-off the commit