Missed a few simples cases from phase 1.a and 1.b of Azure/typespec-azure#4564

Summary

Makes main.tsp import ./client.tsp for services where doing so has no impact on the published OpenAPI, so client customizations are picked up by tsp compile main.tsp.

Group 1 — no config change needed

client.tsp contains only @@clientName/@@alternateType (client-emitter-only). Adding the import is byte-identical to the current swagger:

• monitoringservice/resource-manager/Microsoft.Monitor/Agents
• napster/Napster.CompanionAPI.Management
• programenrollment/resource-manager/Microsoft.ProgramEnrollment/ProgramEnrollment

Group 2 — import + omit-unreachable-types: true

client.tsp declares shadow create/update models that are referenced only by @@alternateType (invisible to the autorest emitter), so the emitter treats them as unreachable. Enabling omit-unreachable-types drops them; enabling the option alone changes nothing in the current output, so the net swagger change is zero:

• applink/AppLink.Management
• edge/Microsoft.Edge.DisconnectedOperations.Management
• relationships/Relationships.Management

Verification

For every service above, regenerating with the autorest emitter produces byte-identical OpenAPI output (verified current-vs-new), and all compile cleanly under --warn-as-error. Only main.tsp (and tspconfig.yaml for Group 2) change; no generated swagger changes.

Not included

The remaining services that don't yet import client.tsp require more involved work and are intentionally excluded:

• @scope-based operation customizations (resources/.../policy, resources/.../deploymentStacks, search) — blocked on autorest honoring @scope (feat(typespec-autorest): add @scope TCGC decorator support typespec-azure#4565).
• Reachable shadow models / @@override / @@clientName-on-operation / property drift (frontdoor, migrate, purviewdatagovernance/DataAccess, storagecache) — need restructuring or a decision on intended output.