[Bug]: should getUnionAsEnum handle extensible boolean?

[qiaozha]

Describe the bug

For typespec, like the below, should we interpret it as an extensible boolean definition?

union A {
  true,
  boolean
}

This is true if we are using the literal number and number types or if we are using the literal string and string types.

Wonder why we handle boolean literal and boolean differently?

In TypeScript, the type infer system will get a boolean

There's also a bug with the typespec-autorest emitter. it will handle the union as an empty object.

Reproduction

playground link

Checklist

• Follow our Code of Conduct
• Check that this issue is about the Azure libraries for typespec. For bug in the typespec language or core libraries file it in the TypeSpec repo
• Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
• The provided reproduction is a minimal reproducible example of the bug.

[markcowl]

won't fix. Not sure what the user scenario is.