Use parameterized error message for ERR_FeatureNotAvailableInVersion

[jcouv]

Currently, every new version requires adding a new error code and diagnostic (for example ErrorCode.ERR_FeatureNotAvailableInVersion7_2). But this could be parameterized instead.

Relates to #19846 (review)

[jcouv]

ErrorCode.cs has a comment regarding telemetry:
ERR_FeatureNotAvailableInVersion1 = 8022, // Note: one per version to make telemetry easier

@dotnet/roslyn-compiler Can anyone confirm whether having a separate error code per language version actually solves any telemetry problem?

[jcouv]

From discussion with Neal, he's not aware of any telemetry benefits of using separate error codes for this specific case. I'll check with Jared too.

[Neme12]

Could we please get a property in the error message that would say which feature the error targets? It would be helpful for a certain kind of code fixes which look for this error to find usages of a language feature that cannot be used in the current language version and offer to convert it to something that does exist in this version (for example an out-var into a declared variable). These fixes would need to know that the diagnostic relates to the feature they're looking for. Would that be possible? Thanks.