Sync space age

[mk-mxp]

This will be the #48in24 exercise on 2024-06-04. Important files changed, but re-running tests on submitted student code not required.

• Documentation sync'ed and checked for mismatches to track tests
• Tests sync'ed with the problem specs
• I did not add the test for a wrong planet, as that makes all existing solutions invalid
• Removed the test for internal storage of seconds, as that should not be tested for

Closes #713

[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!

[homersimpsons]

Everything looks good! Thank you!

About the "wrong planet test", I'm not sure we should skip it though. But as this exercise is rather popular I think this will affect a lot of people.

[mk-mxp]

About the "wrong planet test"

The whole exercise is centered around floating point numbers and very easy. Having exceptions seems odd to me, as we specify all planets as methods explicitly. There are more advanced exercises, where adding such a test makes more sense.

I think that test is for approaches using "planet name to data structure / method / function mapping in student land", where one should actually have such a test. With the complete interface and all methods pre-declared - why should anyone try to use __call() to implement everything dynamically? That would be the only way I see to make use of an exception for a wrong planet.