Format track config with configlet fmt

[BNAndras]

The configlet CI is currently failing because configlet fmt is showing the track config to be unformatted. This is a recently added check for configlet.

[BNAndras]

Right, if I run ./bin/format.sh, we go back to the original formatting that configlet fmt doesn't like. configlet fmt should format the config.json files so maybe prettier shouldn't format those JSON files. That'll let us make both CI checks happy.

[github-actions]

The "Format code" action has started running.

[github-actions]

The "Format code" action has finished running.

[github-actions]

For security reasons, /format does not trigger CI builds when the PR has been submitted from a fork. If checks were not passing due to code format, trigger a build to make the required checks pass, through one of the following ways:

• Push an empty commit to this branch: git commit --allow-empty -m "Trigger builds".
• Close and reopen the PR.
• Push a regular commit to this branch.

[SleeplessByte]

If we want to format it using configlet, we should probably:

• ignore the file using .prettierignore
• update format.sh to call both prettier and configlet.

I would be happy to see that change!

[BNAndras]

I’ll take a look. configlet create now formats the track config as well so that this issue is likely to come up again.

[SleeplessByte]

Understood! Ping me when done or if you cannot figure it out and I'll fix it ;)

[BNAndras]

Last commit was because raindrops has an exercism/note section in the instructions.md. Prettier wanted to revert the tildes to backticks.

[BNAndras]

@SleeplessByte, the CI is passing.