Keep COMPOSE_PROFILES when start scripts add ui or backup profiles

[ArnavAgrawal03]

Summary

Compose ignores COMPOSE_PROFILES whenever a --profile flag is passed. The start scripts passed --profile ui, and since #442 also --profile backup and --profile backup-s3. So turning on scheduled backups silently dropped any profile set in .env, such as ollama.

I hit this in a restore drill on EC2. After restore --restore-config, Morphik started without its Ollama container, so embeddings would have failed.

COMPOSE_PROFILES=ollama in .env:
  docker compose config --services                   -> a o
  docker compose --profile backup config --services  -> a b    (ollama dropped)
  COMPOSE_PROFILES=ollama,backup                     -> a b o

The checked-in start-morphik.sh, the installer-generated copy, and the PowerShell one now add ui, backup, and backup-s3 to COMPOSE_PROFILES instead of passing flags. This also fixes the older ui plus ollama case.

A failed S3 upload now also mentions the EC2 metadata hop limit. The AWS CLI only says "Unable to locate credentials".

Test plan

• pytest core/tests/unit/test_docker_lifecycle.py core/tests/unit/test_docker_installer_safety.py core/tests/unit/test_backup_tool.py: 50 passed. A new test covers COMPOSE_PROFILES="ollama,ui" in .env with backups on, for both the checked-in and the generated script.
• The generated start-morphik.ps1 run under pwsh 7.4 with a stubbed docker gives COMPOSE_PROFILES=ollama,ui,backup,backup-s3 and passes no --profile flags.
• On EC2 host B, the fixed start-morphik.sh started ollama, backup, and backup-s3 together. The restored deployment then matched the original exactly.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}