Remove property for task with undefined behavior (Collatz.yml)

[MartinSpiessl]

This task contains an overflow, so stating the termination
property makes no sense, especially since no verdict is given.

[PhilippWendler]

A case of #480.

[MartinSpiessl]

#480 is related, but Collatz.yml is the only one I found in my experiments with the SV-COMP21 results that has the property without an expected verdict, so I would like to at least fix this such that there is no task without expected verdict in SV-COMP.

#480 is about tasks that have other properties (with expected verdict).

[peterschrammel]

Apparently, the Collatz conjecture has been proven to hold up to at least 2^68 (https://link.springer.com/article/10.1007%2Fs11227-020-03368-x).
The given benchmark implementation will mostly overflow, though, and we don't consider benchmarks with undefined behaviour for termination checks.
If we want to keep a variant of this benchmark for the termination category, we could derive a variant of the benchmark that restricts the input up to a number that doesn't overflow and set the verdict of that variant to true.

[dbeyer]

I like the suggestion to add a new task with a bound. Would you be willing to add it @peterschrammel ? (in another pull request?)