// This is skipped for now. This is a case where we know we can unilaterally mark the reference type as nullable, as long as the user has #nullable enable on.
// But right now there's no compiler API to know if it is, so we have to skip this. Once there is an API, we'll have it always return a nullable reference type
// and we'll remove the ? if it's in a non-nullable context no differently than we always generate types fully qualified and then clean up based on context.