Sync tournament

[mk-mxp]

• Run bin/configlet sync -u -e tournament --yes --docs --filepaths --metadata --tests include (updates the Markdown files and maybe tests.toml)
  • docs: instructions unsynced: tournament
• Drop strict types comments from test file and example code (these are useless)
  • Keep the comment in the students stub file. And the directive itself shall be in all PHP files, too.
• Add and sync test meta data to tests (uuid in DocBlocks / #TestDox())
• Add exercise to bin/auto-sync.txt to keep it in sync (keep the file alphabetically sorted)
• Decide on adding / adjusting / ordering test cases to match current problem specs
  • tournament: missing 12 test cases
• Set difficulty to 5 (medium) in /config.json key exercises.practice.[].difficulty (search for tournament in that file)
• If you wish, add your GitHub handle to the list of contributors in exercises/practice/tournament/.meta/config.json

Do not redesign the student's interface or add test cases that would invalidate existing community solutions. These are extra tasks, which should be discussed in advance.

[resu-xuniL]

Off topic : this exercice is tagged as 'easy'. (compared to other 'easy' exercices, this one is quite ... hard!)
and as I was playing with bash exercices, I saw that this one was tagged as 'medium'.
Is this normal?

[mk-mxp]

We'll fix the difficulty to at least medium, but I think it really is hard. I didn't solve it myself - I haven't found time for exercises since long... Hmm, I solved it, but didn't remember it. It is quite large, but not too difficult. zebra really is hard...