2936 Make comparisons consistent

[ewoutkramer]

This PR removes comparisons from the FHIR types, in favor of using the comparisons on the CQL types. Also, it simplifies the public surface of the CQL types:

• Remove comparison operators from FHIR Date/Time/DateTime/instant
• Replace Result with normal TryXXXX pattern to align better with normal C# use (unfortunately).
• Add convenience methods + interface IToSystemPrimitive for consistently converting from a FHIR primitive to a CQL primitive.

@Kasdejong : The last feature will make sure that doing comparisons in FhirPath is a simple IToSystemPrimitive.TryConvertToSystemType() plus + TryCompare(). We should refactor that in the FP engine.

Still Todo:

• I discovered we have not moved Ratio to Base (which we should) - this would also implement IToSystemPrimitive.
• We now have TryToSystemXXX() and ToSystemXXX() on some types, and just ToSystemXXX() on others. Unify.
• Some types have/had a nullable return for ToSystemXXXX(), which would return null if the Value of the primitive was null. I have now removed that, but double check that that makes sense. Esp with TryXXX: would you return false if you would return null if there is no value, or is that allowed?
• Many of these operations don't have doccomments, need to add that.
• Unit tests
• Document breaking changes

Fixes #2936, also fixes #2932.

[ewoutkramer]

On nullability of ToSytemXXX(), I think we should align with #2990, so throw if the value is null. In the longer term this is also the proposed solution for other "illegal" values in the primitives. In that case Value will throw, and probably so should all the Toxxxx() functions. This means the datatype contains illegal/incomplete information, which is possible since the datatypes also participate in "overflow" (for now, using ObjectValue) and can contain illegal information. Rather than allowing a user to inadvertedly continue working with that information, we should throw when he/she tries to "do" something with it.