Add FDC3 2.2 conformance tests and deployment-aware AppD URLs

[Copilot]

Describe your change

Adds two new FDC3 2.2 conformance tests per test-pack specification and makes conformance framework deployment-aware for netlify previews, localhost, and production.

Changes

Conformance Tests

• Manual ChannelChangedEvent test verifying event listener behavior
• Additional test coverage from test-pack specification
• Updated FDC3 Demo implementation to pass new manual tests

Deployment Infrastructure

• AppD URLs now relative to hosting environment (preview/localhost/production)
• Added replaceConformanceUrls.js script for dynamic URL injection
• Created preview-conformance.v2.json and website-conformance.v2.json app directories

Fixes

• Fixed broadcast handler duplicate context handling for instanceIds
• Corrected WCP1Hello schema property name in HelloHandler
• Updated test timing constants for reliability across platforms

Dependencies

• Updated package-lock.json for consistency
• Fixed js-yaml and other dependency vulnerabilities

Related Issue

Resolves #1455, #1611
Raises #1585

Contributor License Agreement

• I acknowledge that a contributor license agreement is required and that I have one in place or will seek to put one in place ASAP.

Review Checklist

• Issue: If a change was made to the FDC3 Standard, was an issue linked above?
• CHANGELOG: Is a CHANGELOG.md entry included?
• API changes: Does this PR include changes to any of the FDC3 APIs (DesktopAgent, Channel, PrivateChannel, Listener, Bridging)?
  • Docs & Sources: If yes, were both documentation (/docs) and sources updated?
    
    JSDoc comments on interfaces and types should be matched to the main documentation in /docs
  • Conformance tests: If yes, are conformance test definitions (/toolbox/fdc3-conformance) still correct and complete?
    
    Conformance test definitions should cover all required aspects of an FDC3 Desktop Agent implementation, which are usually marked with a MUST keyword, and optional features (SHOULD or MAY) where the format of those features is defined
  • Schemas: If yes, were changes applied to the Bridging and FDC3 for Web protocol schemas?
    
    The Web Connection protocol and Desktop Agent Communication Protocol schemas must be able to support all necessary aspects of the Desktop Agent API, while Bridging must support those aspects necessary for Desktop Agents to communicate with each other
    • If yes, was code generation (npm run build) run and the results checked in?
      
      Generated code will be found at /src/api/BrowserTypes.ts and/or /src/bridging/BridgingTypes.ts
• Context types: Were new Context type schemas created or modified in this PR?
  • Were the field type conventions adhered to?
  • Was the BaseContext schema applied via allOf (as it is in existing types)?
  • Was a title and description provided for all properties defined in the schema?
  • Was at least one example provided?
  • Was code generation (npm run build) run and the results checked in?
    
    Generated code will be found at /src/context/ContextTypes.ts
• Intents: Were new Intents created in this PR?
  • Were the intent name prefixes and other naming conventions & characteristics adhered to?
  • Was the new intent added to the list in the Intents Overview?

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.