Using a workflow to trigger mirroring instead of a webhook allows us to
reuse "Approving workflow runs from public forks" GitHub feature to
somewhat protect us from malicious PRs

Closes #203. This will be the first release to crates.io:

- Use crates.io dependencies, remove chain extension #204

Use all substrate/polkadot-sdk dependencies from crates.io, remove
`pallet-asset-chain-extension` so we can release this to crates.io. See
#203

Sync with `polkadot-v1.0.0` in order to include
https://github.com/paritytech/substrate/pull/14642.

Fixes #200

Updates lockfile to point to `polkadot-1.0.0` HEAD, to include the
enabling of `sign_ext`

- [x] Needs update of
https://github.com/727-Ventures/pallet-assets-chain-extension to
`polkadot-v1.0.0`
- [x] Diff and apply commits between `0.9.43` and `1.0.0`

Required for https://github.com/paritytech/ink/pull/1795 and
https://github.com/paritytech/cargo-contract/pull/1149

#180 upgraded to
[polkadot-v0.9.42](https://github.com/paritytech/substrate/tree/polkadot-v0.9.42).

This PR bumps the version to `0.26.0` in preparation for a release tag.

As discussed with @Kianenigma, @PierreBesson

 and others, this pull
request brings the ability to spin up a Codespace instance inside this
repository. The PR has two components:

- `devContainer.json`: The setup instructions to initialize the instance
with
- `updateContentCommand.sh`: A custom shell script to install the necessary
dependencies for Substrate and the contracts node template on the
Codespace instance that is invoked immediately after the instance is
created

It also includes a badge in the README to allow users to start a Codespace instance using these settings from their own GitHub account.

---------

Co-authored-by: Ben Greenberg <[email protected]>
Co-authored-by: German <[email protected]>
Co-authored-by: Sacha Lansky <[email protected]>
Co-authored-by: Sasha Gryaznov <[email protected]>

In recent PR
https://github.com/paritytech/substrate-contracts-node/pull/182#issuecomment-1536514910,
the CI step of running `cargo test` was commented out as a dirty
workaround for the pallet contracts integrity test failure. The test
checks that the pallet configuration is memory safe.

So to make the test pass, we enlarge the runtime memory limit in the
Schedule. We do this because this development node
[allows](https://github.com/paritytech/substrate-contracts-node/blob/8d13ddef3f5c728d1661e79c511a28cef206b298/runtime/src/lib.rs#L367)
larger contract size than it is normally allowed in a production running
node. This should be fine for the development node where possible
security implications could be neglected for the sake of development
convenience. **However, please DO NOT do this to your production node
config, unless you are sure that the limit you're setting is the real
memory limit of your runtime**.

This is needed in order to make the e2e test for
[call_runtime](https://github.com/paritytech/ink/blob/e267dd15730c3d19d5030fa440292f849acf9960/integration-tests/call-runtime/lib.rs#L150)
pass

Minor improvements including spelling and fixing broken links.

This flag got removed from Substrate a while ago.

Related issue: https://github.com/paritytech/ink/issues/1007

PR changes ci runners for dynamically created ones

cc https://github.com/paritytech/ci_cd/issues/730

Sync the repository with Substrate's
[polkadot-v0.9.37](https://github.com/paritytech/substrate/tree/polkadot-v0.9.37)
branch.

The utility pallet is required for batch transactions to work in
polkadot-js and should therefore be included in the substrate contracts
node.

See
https://github.com/polkadot-js/api/issues/4801#issuecomment-1120629488
for details.

Sync the repository with Substrate's
[`polkadot-v0.9.34`](https://github.com/paritytech/substrate/tree/polkadot-v0.9.34

)
branch.

Co-authored-by: Bastian Köcher <[email protected]>
Co-authored-by: Alexander Theißen <[email protected]>

- Removed some flat out unused dependencies
- Remove last pieces of (defunct) benchmarking infrastructure
- Remove rocksdb: It takes notoriously long to build and there is no
reason why we shouldn't use parity-db for this dev node

* Update lockfile

* Bump manifest

* Update to polkadot-v0.9.32

* Bump lockfile

* Update README

Co-authored-by: Alexander Theißen <[email protected]>

* Update to polkadot-v0.9.31

* Remove runtime benchmarks

* Remove try-runtime

* Added support of `pallet-assets` and chain extension for it.

* Updated obce and extension to use `polkadot-v0.9.29`

* Moved `pallet-assets` to all pallets

* Track polkadot-v0.9.29

* Update lockfile

* Update README

* apply 324a18e

* sync up to 1c0d008

* sync with 1c0d008 and readme update

* set correct commit hash

* sync with #021f712

* Use resolver v2

* Sync with substrate

* Add new payment info runtime API

* Make dev chain spec the default

* Set sane log filtering by default

* Update README.md

Co-authored-by: Michael Müller <[email protected]>

Co-authored-by: Michael Müller <[email protected]>

* Add guide for synchronizing with Substrate

* Change `rm Cargo.lock` instruction

* Update sync instructions

* Remove breaking change note