fix(calm-hub): make mongo initialization log consistent

[markscott-ms]

Description

Recent additions of controls, domains and decorators led to some inconsistent logging during MongoDB initialisation, and a JSON syntax in /calm/architecture/calm-2.json

This PR fixes that.

No functionality change - just print statements.

$ mongosh mongo/init-mongo.js 
  ✅ Using database: calmSchemas
=== Counters ===
  - patternStoreCounter already exists, no initialization needed
  - architectureStoreCounter already exists, no initialization needed
  - adrStoreCounter already exists, no initialization needed
  - standardStoreCounter already exists, no initialization needed
  - flowStoreCounter already exists, no initialization needed
  - userAccessStoreCounter already exists, no initialization needed
  - controlStoreCounter already exists, no initialization needed
  - decoratorStoreCounter already exists, no initialization needed
=== Schemas ===
  ❌ Schema directory not found at /calm/release, skipping
  ❌ Set CALM_SCHEMA_BASE_PATH environment variable to load schemas from a different location
...

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/)
• Schema (calm/)
• CALM AI (calm-ai/)
• CALM Hub (calm-hub/)
• CALM Hub UI (calm-hub-ui/)
• CALM Server (calm-server/)
• CALM Widgets (calm-widgets/)
• Documentation (docs/)
• Shared (shared/)
• 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

[aamanrebello]

Looks good!

[markscott-ms]

Thanks @aamanrebello . I'm going to mark this PR as draft as I'll need to make an update after @harveymmaunders 's PR #2285 is merged.