[Bug]: visibility discrepancy between Swagger and TypeSpec defined UserAssignedIdentity

[XiaofeiCao]

Describe the bug

TypeSpec:

typespec-azure/packages/typespec-azure-resource-manager/lib/common-types/managed-identity.tsp

Lines 95 to 101 in a633ee1

	model UserAssignedIdentity {
	@doc("The active directory client identifier for this principal.")
	clientId?: string;
	@doc("The active directory identifier for this principal.")
	principalId?: string;
	}

Swagger:

"UserAssignedIdentity": {
  "type": "object",
  "description": "User assigned identity properties",
  "properties": {
    "principalId": {
      "description": "The principal ID of the assigned identity.",
      "format": "uuid",
      "type": "string",
      "readOnly": true
    },
    "clientId": {
      "description": "The client ID of the assigned identity.",
      "format": "uuid",
      "type": "string",
      "readOnly": true
    }
  }
}

The model is used in both input and output.
For input, user sends something like:

{
  "userAssignedIdentities": {
    "00000000-0000-0000-0000-000000000000": {}
  }
}

For output, service will reply:

{
  "userAssignedIdentities": {
    "00000000-0000-0000-0000-000000000000": {
      "principalId": <some-principal-id>,
      "tenantId": <some-tenant-id>
    }
  }
}

If not defined with @visibility("read"), unnecessary setter methods will be generated for Java.

Reproduction

See above

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.

[allenjzhang]

fixed in pending PR #945