Improve descriptions to make sense per #1769

[wolf99]

Fixes #1769

There were cases where the descriptions where the data did not numerically match the descriptions, such as

      "description": "1000 is a single M",
      "input": {
        "number": 1024
      },
      "expected": "MXXIV"

1. Leave as-is
2. Change the description to match the data
3. Change the data to match the description

There is a slight semantic difference between 2 and 3 if you consider that what this case is testing is not just explicitly that 1024 is MXXIV, but that absent any other test to the effect it also implicitly tests that 1000 is M as the original description states.

I chose 2 as it accurately describes what the test is doing, but 3 is probably as valid a change

[ErikSchierboom]

@wolf99 I completely support these changes. They nicely follow our documentation that still says that the description is immutable. We've had some discussion on that in another issue (do you remember which issue @SleeplessByte?) and the conclusion there is that changing the description is fine too. Could you update the PR accordingly? I'll submit a different PR to update the documentation.

[wolf99]

We've had some discussion on that in another issue

Is in the review comments on #1747 I believe.

I will update my PR per your suggestion this evening then.

[ErikSchierboom]

Do we need the is a single bit in the description? It looks like it was removed from other test cases.

[wolf99]

Whoops, I missed this in the update.
Well caught Erik

[ErikSchierboom]

LGTM

[valentin-p]

LGTM