Labels in issue templates

[cameel]

argotorg/solidity-blog#159 (comment) by @christianparpart gave me and idea that we could automatically apply labels in our issue templates.

The PR also does some minor cleanup in templates:

• Replaces tabs with spaces
• Removes hard wrapping to make the instructions look more concise. Text in Github's issue editor is always soft wrapped. It also will never show up in the preview and even if it did, Github does not remove hard wrapping when rendering issue comments as would normally happen in markdown.

[christianparpart]

Do we want to reference the linked Matrix chat here?

[cameel]

Personally, I always give people the gitter link because it just drops you directly on the channel without having to go through any nag screens about downloading the client.

Maybe we should list both?

[chriseth]

That is true, so let's stay with gitter as long as it still works.

[chriseth]

Currently (at least that's how I have handled it), the label served the purpose of "confirmed bug". What do we want to do about that? Just keep the label and use the project columns to track confirmed / not confirmed?

[cameel]

Yeah, I had doubts about this myself because of that system. Maybe we should actually change it? I think it would be useful to have this stuff immediately categorized and a confirmed label would have more obvious meaning - the current system is a bit too implicit.

But I can remove it from the template if you prefer to stay with the current system.

[chriseth]

let's use the columns in the project to mark it as confirmed.

[cameel]

ok, so not in New issues means that it's confirmed?

[chriseth]

yes