Upgrade upstream 2.0.0 (#2)

* 🔖 update image

* Updated base image

* 🔖 update image

* Create Issue templates (#73)

* Create Issue templates

- Report a Bug
- Suggest a Feature
- Ask a Question

* 🔖 update image

* Only run build action in main repo

* 🔖 update image

* Upgrade to v2.0.0-rc6 (#75)

* 🔖 update image

* Simplify docker image creation workflow

* Backport paritytech/substrate#7014 (#81)

* Update to v2.0.0 🎉 (#88)

* Update Dockerfile

* Update Dockerfile

* Add toolchain file (#92)

* Add toolchain file

* Remove reference to script that uses latest nightly

* Remove link to nonexistent subheading

* Update devcontainer.json

* Delete Dockerfile

* Added nicer commands

* Rely on latest image

* Added new menu option

* Update toolchain file to be compatible with paritytech/ci-linux Docker (#98)

Closes #95

* Remove rust-toolchain file (#99)

Architecture specific toolchains are not allowed in this file.
We can assume that stable is the default toolchain and should not
dictate with which toolchain the user builds the client. Also this
breaks under macOS.

We are only interested with which toolchain the runtime is build.
For this we should set the WASM_BUILD_TOOLCHAIN variable.

* Bump wasm-builder-runner

1.0 wasm-builder-runner is not compatible with 2.0 wasm-builder paritytech/substrate#7283 (comment)

* Nix shell sync with Substrate (#100)

* nix shell config

* fix darwin

* update nightly for nix shell

* fix deps

Co-authored-by: Dan Forbes <dan@parity.io>
Co-authored-by: Julien Eluard <jeluard@users.noreply.github.com>
Co-authored-by: Alexander Theißen <alex.theissen@me.com>
Co-authored-by: Xiliang Chen <xlchen1291@gmail.com>
Co-authored-by: Bastian Köcher <bkchr@users.noreply.github.com>
Co-authored-by: kaichao <kaichaosuna@gmail.com>

.github/ISSUE_TEMPLATE/ask-a-question.md

@@ -0,0 +1,13 @@
+---
+name: Ask a Question
+about: Ask a question about this template.
+title: ""
+labels: question
+assignees: ""
+---
+
+**Question**
+
+_Please include information such as the following: is your question to clarify an existing resource
+or are you asking about something new? what are you trying to accomplish? where have you looked for
+answers?_

.github/ISSUE_TEMPLATE/report-a-bug.md

@@ -0,0 +1,46 @@
+---
+name: Report a Bug
+about: Report a problem with this template.
+title: ""
+labels: bug
+assignees: ""
+---
+
+**Description**
+
+_Tell us what happened. In particular, be specific about any changes you made to this template.
+Ideally, provide a link to your project's GitHub repository. Please note that we are not able to
+support all conceivable changes to this template project, but the more information you are able to
+provide the more equipped we will be to help._
+
+**Steps to Reproduce**
+
+_Replace the example steps below with actual steps to reproduce the bug you're reporting._
+
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected vs. Actual Behavior**
+
+_What did you expect to happen after you followed the steps you described in the last section? What
+actually happened?_
+
+**Environment**
+
+_Describe the environment in which you encountered this bug. Use the list below as a starting point
+and add additional information if you think it's relevant._
+
+- Operating system:
+- Template version/tag:
+- Rust version (run `rustup show`):
+
+**Logs, Errors or Screenshots**
+
+_Please provide the text of any logs or errors that you experienced; if
+applicable, provide screenshots to help illustrate the problem._
+
+**Additional Information**
+
+_Please add any other details that you think may help us solve your problem._

.github/ISSUE_TEMPLATE/suggest-a-feature.md

@@ -0,0 +1,26 @@
+---
+name: Suggest a Feature
+about: Suggest a new feature or an improvement to an existing feature for this template.
+title: ""
+labels: enhancement
+assignees: ""
+---
+
+**Motivation**
+
+_Describe the need or frustration that motivated you to make this suggestion. Please note that the
+goal of this project is to provide a general-purpose template project, so please take care when
+suggesting features that may be specific to a particular use case._
+
+**Suggested Solution**
+
+_Describe your suggested solution to the need or frustration that you are experiencing._
+
+**Alternatives**
+
+_Describe any alternative solutions or features you considered and why you believe your suggested
+solution is preferable._
+
+**Additional Information**
+
+_Provide any additional information that you believe may help us evaluate your suggestion._