fix: narrow ARM metadata filter to only strip exclusively read-only properties

[Copilot]

In ARM mode, the metadata property filter in buildModelInterface was stripping @path properties from any model where the property's visibility set contained Visibility.Read — including plain parameter bag models with no ARM base class. Since @path properties carry multiple visibility flags (Read | Create | Update | ...), they were incorrectly filtered out, producing empty interfaces and downstream TypeScript compile failures.

Changes

• src/modular/emitModels.ts — Tighten the ARM metadata filter condition from p.visibility?.includes(Visibility.Read) to p.visibility?.length === 1 && p.visibility?.includes(Visibility.Read), so only properties that are exclusively read-only are removed.

• test/modularUnit/scenarios/models/arm/pathPropertyInParameterBag.md — New scenario test reproducing the reported pattern: an ARM service with a plain PrivateLinkParameters model carrying a @path privateLinkName property. Verifies the property survives into the generated interface.

• test/modularUnit/scenarios/models/arm/armReadCreateVisibility.md — Scenario test verifying a @path property with Read & Create visibility is preserved in the generated interface.

• test/modularUnit/scenarios/models/arm/armReadOnlyVisibility.md — Scenario test verifying a @path property with exclusively Read visibility is correctly stripped (interface remains empty).

• test/modularUnit/scenarios/models/arm/armReadUpdateCreateVisibility.md — Scenario test verifying a @path property with Read & Update & Create visibility is preserved in the generated interface.

- p.visibility?.includes(Visibility.Read)
+ p.visibility?.length === 1 && p.visibility?.includes(Visibility.Read)

Before fix:

export interface PrivateLinkParameters {}  // @path property stripped

After fix:

export interface PrivateLinkParameters {
  privateLinkName: string;  // correctly preserved
}

[kazrael2119]

@copilot could you add more uts about visibility cases like Read & Create, Read, Read & Update & Create?

[Copilot]

@copilot could you add more uts about visibility cases like Read & Create, Read, Read & Update & Create?

Added three new scenario files in test/modularUnit/scenarios/models/arm/ (commit 5b2dc63):

• armReadCreateVisibility.md — @visibility(Lifecycle.Read, Lifecycle.Create) → property preserved in interface
• armReadOnlyVisibility.md — @visibility(Lifecycle.Read) only → property stripped (interface is empty {})
• armReadUpdateCreateVisibility.md — @visibility(Lifecycle.Read, Lifecycle.Update, Lifecycle.Create) → property preserved in interface

[JialinHuang803]

There are four ut files for this case. Does it make sense to combine them into one?

[kazrael2119]

@copilot could you resolve this comment?

[Copilot]

Done in commit 94b2fca. All four scenario files are now consolidated into a single armMetadataFilter.md with four #-level scenarios (default multi-flag @path, Read & Create, Read only, and Read & Update & Create).