CALM Schema 1.1: revised 'flows' definition

[markscott-ms]

Description

The preparation for the Advent of CALM identified that the flows schema in CALM 1.0 fails to correctly require that transition objects has certain fields.

CALM Schema 1.1 is a minor update to the schema that fixes this.

I have added tests for validation, showing the failed validation for 1.0, and accurate validation against 1.1.

No changes have been made to the schema outside of flows.

This is not a breaking change because the schema is new. Users of flows in 1.0 who have not defined transitions as intended will need to fix it in the upgrade to schema 1.1.

It is noted that the Chatmode files have the correct schema.

Fixes #1856

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🎨 Code style/formatting changes
• ♻️ Refactoring (no functional changes)
• ⚡ Performance improvements
• ✅ Test additions or updates
• 🔧 Chore (maintenance, dependencies, CI, etc.)

Affected Components

• CLI (cli/)
• Shared (shared/)
• CALM Widgets (calm-widgets/)
• CALM Hub (calm-hub/)
• CALM Hub UI (calm-hub-ui/)
• Documentation (docs/)
• VS Code Extension (calm-plugins/vscode/)
• Dependencies
• CI/CD

Commit Message Format ✅

Testing

• I have tested my changes locally
• I have added/updated unit tests
• All existing tests pass

Checklist

• My commits follow the conventional commit format
• I have updated documentation if necessary
• I have added tests for my changes (if applicable)
• My changes follow the project's coding standards