Logically, it makes more sense to provide the steps leading up to the bug before asking what the bug is. This change moves "steps to reproduce" above "expected behavior" and "actual behavior" to enforce the above progression and logical flow.

* Update .ruby-version

* Update Gemfile

* Update Gemfile.lock

* Update Dockerfile

* Update check-i18n.yml

* Update config.yml

* Update config.yml

* Build container image by GitHub Actions

* Trigger docker build only pushed to main branch

* Tweak tagging imgae

- "edge" is the main branch
- "latest" is the tagged latest release

* Change references to tootsuite/mastodon to mastodon/mastodon

* Remove obsolete test fixture

* Replace occurrences of tootsuite/mastodon with mastodon/mastodon in CHANGELOG

And a few other places

* Update dependabot.yml

* Update dependabot.yml

* Delete config.yml

* Create dependabot.yml

- https://help.github.com/en/articles/displaying-a-sponsor-button-in-your-repository

* Update issue templates

* Update bug_report.md

* Update feature_request.md

* Update support.md

* Update feature_request.md

* Multiple Issue templates

* Update bug_report.md