Nullness - downcasting and typetests should understand nullness information

[T-Gro]

Addresses #17532

This revisits what downcasts and typetests do in the context of nullability analysis.
In the end, both unboxing and typetests are a runtime instruction, which is not aware of any nullability in the form | null. It is aware of internal nullability of NullTrueValue F# types, like option and unit.

The following is ensured:

• Downcasting from a value which can carry null into a WithoutNull one gives a new warning
• Downcasting from a non-nullable value into nullable gives (existing) warning about type erasure
• Typetesting againts nullable versions of types gives warning about type erasure (the "isinst" instruction will always return false for null in the source, so typetesting for nullable versions does not make sense - except for type where null is a true value, where the FSharp.Core function understands this and special-cases types like unit and option)

The UnboxGeneric function in F# Core, in its current version, is doing a runtime test against null and throws if the runtime-known information is not a type accepting null. However, this is runtime and reflection, not aware of nullable analysis.
For that reason, downcasting into | null versions of types, including nullable generic type parameters, now avoid this UnboxGeneric call and immediately go to the unbox.any instruction (which turns null in the input into null in the output, instead of throwing).

[github-actions]

❗ Release notes required

---

✅ Found changes and release notes in following paths:

Change path	Release notes path	Description
src/Compiler	docs/release-notes/.FSharp.Compiler.Service/9.0.200.md

[T-Gro]

/run fantomas

[github-actions]

Ran fantomas: https://github.com/dotnet/fsharp/actions/runs/11709404820