[Bug]: Normalization on the x-ms-enum name if only value and description is specified

[allenjzhang]

Describe the bug

Should we normalize the name in the x-ms-enum so swagger & codegen could get correctly named entries?

union ManagedServiceIdentityType {
  /** No managed identity. */
  "None",
  "SystemAssigned, UserAssigned",   <---- contains space and coma
  string,
} 

      "x-ms-enum": {
        "name": "ManagedServiceIdentityType",
        "modelAsString": true,
        "values": [
          {
            "name": "None",
            "value": "None",
            "description": "No managed identity."
          },
          {
            "name": "SystemAssigned, UserAssigned",    <----- We should normalize the name here and not take as it is.
            "value": "SystemAssigned, UserAssigned",
            "description": "System and user assigned managed identity."
          }
        ]
      }

Reproduction

See code above

Checklist

• [X] Follow our Code of Conduct
• [X] 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
• [X] Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
• [X] The provided reproduction is a minimal reproducible example of the bug.

[markcowl]

Why not use a named union in this case? Our automatically generated name is unlikely to be what we actually want to use in clients in many cases.

[timotheeguerin]

autorest was able to do something without values I don't think we need to be the ones inventing names here. Either the user provided one and we carry it over or we delegate teh logic to the other emitters