Sync series (issue #988)

[resu-xuniL]

• Synced series metadata and docs
• Removed strict types comments from example.php and SeriesTest.php
• Added UUID and TestDox to tests
• Added missing / edit tests
• Added series to auto-sync.txt
• Added GitHub handle to config.json

Ref: #988

Closes #988

[github-actions]

This PR touches files which potentially affect the outcome of the tests of an exercise. This will cause all students' solutions to affected exercises to be re-tested.

If this PR does not affect the result of the test (or, for example, adds an edge case that is not worth rerunning all tests for), please add the following to the merge-commit message which will stops student's tests from re-running. Please copy-paste to avoid typos.

[no important files changed]

For more information, refer to the documentation. If you are unsure whether to add the message or not, please ping @exercism/maintainers-admin in a comment. Thank you!

[mk-mxp]

Hmm, did I forget to say: Your AI should not phantasize but you should synchronize to the canonical repo: https://github.com/exercism/problem-specifications/blob/main/exercises/series/canonical-data.json That why it's "synchronize"...

Sorry if that was unclear. Please adjust the test data.

[resu-xuniL]

Hmm, did I forget to say: Your AI should not phantasize but you should synchronize to the canonical repo: https://github.com/exercism/problem-specifications/blob/main/exercises/series/canonical-data.json That why it's "synchronize"...

Sorry if that was unclear. Please adjust the test data.

Sorry about that, i didn't knew that such a file exist (canonical-data.json) and I tried to come up with my own solution (100% AI free).

Working on this now

[resu-xuniL]

1. Should the error messages be implemented ?
   (I see "expected": { "error": "slice length cannot be greater than series length" } in the canonical-data.json file
2. should the Exception::class be changed to InvalidArgumentException::class

--> It breaks the tests (if I run composer test:run -- series they are failures)

[mk-mxp]

To 1.: No, it's usually better to not expect a certain message in these exercises.

To 2.: Exception was chosen a long time ago, and we should stick with it. For a new exercise InvalidArgumentException would be prefered.

And of course: No AI is totally great! That was a great deal of work then... I'm sorry I missed to give that part of the first-time contributer information.

[resu-xuniL]

Ok, I drop the last commit then.
Thanks for answering.