test(client): support read-only clients

[jason-ha]

Update presence multi-client testing to have tests with a single writer and all others read only.

Add test infrastructure support to have uniquely reader clients in a session. Token provider need only specify write scope during attach.

  Presence with AzureClient
    ✔ announces 'attendeeConnected' when remote client joins session [5 clients, 5 writers]
    ✔ announces 'attendeeDisconnected' when remote client disconnects [5 clients, 5 writers]
    ✔ announces 'attendeeConnected' when remote client joins session [5 clients, 1 writers]
    ✔ announces 'attendeeDisconnected' when remote client disconnects [5 clients, 1 writers]
    ✔ announces 'attendeeConnected' when remote client joins session [20 clients, 20 writers]
    ✔ announces 'attendeeDisconnected' when remote client disconnects [20 clients, 20 writers]
    ✔ announces 'attendeeConnected' when remote client joins session [20 clients, 1 writers]
    - announces 'attendeeDisconnected' when remote client disconnects [20 clients, 1 writers]

The base branch was changed.

[Copilot]

Pull Request Overview

This PR adds support for read-only clients in multi-client presence testing by introducing scope-based access control. The change allows configuring one client as a writer (leader) and all others as read-only participants.

• Add scope parameters to control client permissions during connection and container creation
• Refactor token provider to support different scopes for attach vs regular operations
• Update multi-process test infrastructure to designate first client as writer and others as readers

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
orchestratorUtils.ts	Modified to create first client with write permissions and added scope parameters to connection messages
messageTypes.ts	Added scope fields to ConnectCommand interface for specifying client permissions
childClient.ts	Updated to pass scope parameters through to token provider and removed unused imports
AzureTokenFactory.ts	Added attachScopes parameter to support different permissions for container creation
insecureTokenProvider.ts	Refactored to consolidate token generation logic and support separate attach scopes

[WillieHabi]

This is just a question -- so here we want to test both with attendee connect and disconnect with all write clients and then with all read clients?

[jason-ha]

Not quite - all write and then 1 write with rest read