Tracking for Release v0.17.0 (#562)

Release tracker for v0.17.0 of chorus, set to release on October 10th,
2024.

## Public API changes

- #561: Add missing fields in `GatewayReady` event, create
`GatewayReadyBot` for Bots
- #560: Differentiate between instance softwares through /version and
/ping endpoints
- #537: Implement 30 user routes
- #565 : Fix sqlx En-/Decoding of PremiumType
- #567

## Internal changes

## Bugfixes

- #565 : Fix sqlx En-/Decoding of PremiumType

.github/workflows/build_and_test.yml

@@ -97,6 +97,7 @@ jobs:
         with:
           cache-all-crates: "true"
           prefix-key: "macos"
+      - uses: taiki-e/install-action@nextest
       - name: Run WASM tests with Safari, Firefox, Chrome
         run: |
           rustup target add wasm32-unknown-unknown
@@ -126,6 +127,7 @@ jobs:
         with:
           cache-all-crates: "true"
           prefix-key: "macos"
+      - uses: taiki-e/install-action@nextest
       - name: Run WASM tests with Safari, Firefox, Chrome
         run: |
           rustup target add wasm32-unknown-unknown

CONTRIBUTING.md

@@ -10,3 +10,7 @@ ever since [we streamlined the process of doing so](https://github.com/polyphony
 
 If you'd like to contribute new functionality, check out [The 'Meta'-issues.](https://github.com/polyphony-chat/chorus/issues?q=is%3Aissue+label%3A%22Type%3A+Meta%22+) They contain a comprehensive list of all features which are yet missing for full Discord.com compatibility.
 Please feel free to open an Issue with the idea you have, or a Pull Request.
+
+## Merging
+
+All pull requests opened into the `dev` branch should be merged via the "Squash and Merge" option to keep the commit history small. Merging into the `main` branch should be done via a regular merge commit. This way, GitHub will correctly attribute contributors and count statistics for the insights tab.