Do we still need `@knownValues` now that we can do union with string option?

[timotheeguerin]

We kept it as it was a way to define a set of known values for a string when azure was just using enum and fixed but now that we can use named union with a string option and name values this feels just more verbose with no benefit