[core] Fix enum-driven visibility consistency issues when projections are used

[witemple-msft]

• Changed getLifecycleVisibilityEnum to honor projections when program is a ProjectedProgram.
• Taught Projector to project EnumValue values only, so that they remain consistent with projected Enum and EnumMember references. If the projection of the underlying EnumMember does not result in another EnumMember (i.e. it projects to some other type, which I think should be rare, but possible according to the type system), the projector gives up and returns the original enum member.

A more complex solution would try to project all values, but this could damage the scalar hierarchy and there is an open issue to consider removing projections in favor of mutators in the future.

Closes #5450
Closes #5461

[azure-sdk]

All changed packages have been documented.

• ✅ @typespec/compiler

Show changes

@typespec/compiler - fix ✏️

Enum-driven visibility decorators and projections now interact correctly.,> ,> Projections now project EnumValue values to preserve consistency with projected Enum/EnumMember types using a best-effort,> strategy.

[azure-sdk]

You can try these changes here

🛝 Playground	🌐 Website	📚 Next docs	🛝 VSCode Extension

[witemple-msft]

• [Bug]: Invisible decorator doesn't work #5450: Playground

No error as expected

• [Bug]: @defaultVisibility decorator does not recognize member of class enum #5461: Playground

validated property removed from schema User as expected.

[bterlson]

I approve of this hack.