[v3] Prepare for v3

[ErikSchierboom]

This issue is part of the migration to v3. You can read full details about the various changes here.

This PR prepares the track for Exercism v3, which will be different in a number of ways from Exercism v2.

As having this PR merged is essential to prepare this track for Exercism v3, we'll automatically merge this PR one week after it was opened (if it hasn't been merged already).

In this PR, the following changes are made:

v2 file migration

1. Move the existing exercises in the exercises directory to the exercises/practice directory

v3 file migration

1. Copy the v3 languages/<slug>/concepts directory to the concepts directory
2. Copy the v3 languages/<slug>/exercises/concept directory to the exercises/concept directory
3. Copy the v3 languages/<slug>/reference directory to the reference directory
4. Copy the v3 languages/<slug>/docs directory to the docs directory

Notes

Any commits modifying the aforementioned directories (or any of their files) are included in the PR, except for:

• The _sidebar.md files are not migrated
• The README.md file at the v3 track's root is not migrated.
• The maintainers.md file is not migrated.

config.json migration

The config.json file is updated to conform to the v3 spec.

1. Add a version property:

"version": 3

2. Add online editor settings:

"online_editor": {
  "indent_style": "space",
  "indent_size": 2
}

3. Rename the "exercises" property to "practice"

4. Create an "exercises" property and move the "practice" property to this property:

"exercises": {
  "practice": [
    ...
  ]
}

5. Remove the "core", "auto_approve", and "unlocked_by" properties from the practice exercises

6. Add the "name" property to the practice exercises and pre-populate this with a titlelized version of the "slug" property

7. Add the "prerequisites" property to the practice exercises and set it to an empty array

8. Add an empty "concept" array property to the "exercises" property

"exercises": {
  "concept": [],
  "practice": [
    ...
  ]
}

9. Move the "foregone" property to the "exercises" key:

"exercises": {
  ...
  "foregone": [...]
}

10. Add a top-level "concepts" key, which is an array:

"concepts": []

11. Add a top-level "tags" key, which is an array:

"tags": []

12. Add a top-level "key_features" key, which is an array:

"key_features": []

13. Add a top-level "status" key, which is an object containing properties with boolean values indicating if a v3 feature is implemented:

"status": {
  "concept_exercises": true,
  "test_runner": true,
  "representer": false,
  "analyzer": false
}

14. Add a top-level "slug" key, which is a string containing the track's slug:

"slug": "csharp"

15. Re-order the practice exercises using the following ordering:

    1. Core exercises, retaining their existing ordering
    2. Non-core exercises, ordered by the order of the core exercise that unlocks them, then by difficulty and then alphabetically.
    3. Bonus exercises, ordered by difficulty then alphabetically.

16. Add the "status" key with a value of "deprecated" to practice exercises that have "deprecated" set to true. The deprecated field itself is removed:

{
  "slug": "octal",
  "name": "Octal",
  "uuid": "f29f9e56-c79b-4ae4-a0d0-29db78c677e4",
  "prerequisites": [],
  "difficulty": 0,
  "topics": ["integers"],
  "status": "deprecated"
}

Notes

• Settings defined in the v3 config.json file will take precedence over their v2 config.json file's equivalent.

configlet

1. Update the fetch-configlet and fetch-configlet.ps1 files to the latest version of configlet, which can work with v3 tracks.

Continuous integration

1. Add a GitHub Actions workflow to verify the track using the configlet-CI GitHub Action, unless there already is a file named .github/workflows/configlet.md.

2. Add a dependabot configuration to automatically submit PRs for any new versions of external workflows used in this track's GitHub Action workflows.

3. Convert any Exercism GitHub Actions workflows being used to use main as their branch instead of master. See this issue.

Follow-up steps

We've created issues in this repo for the follow-up steps to get this track ready for v3.

Tracking

https://github.com/exercism/v3-launch/issues/11