feat(mlflow): document KOTS auto-update behavior with HelmChart weight ordering

Parent epic: #166
Integration branch: feat/mlflow-enterprise-patterns

Document how KOTS auto-deploy behaves with multi-chart HelmChart weight ordering, including known edge cases.

Scope

• Add autoDeploy field to release/kots-app.yaml if not present
• Create applications/mlflow/docs/auto-update.md covering:
  • How auto-deploy interacts with HelmChart weight ordering (infra weight -10 → mlflow weight 10)
  • What happens during operator upgrades (CRD changes, etc.)
  • Edge cases: config field changes requiring re-deploy, semver rollback behavior, required versions
  • Recommended settings for production vs development channels
• Link from main README.md to the new doc

Files touched

• applications/mlflow/release/kots-app.yaml (add autoDeploy field)
• applications/mlflow/docs/auto-update.md (new file)
• applications/mlflow/README.md (add link)

PR target

Branch PRs to feat/mlflow-enterprise-patterns (not main).

Start by inspecting applications/mlflow/release/kots-app.yaml, applications/mlflow/README.md, and the existing MLflow application structure on feat/mlflow-enterprise-patterns. Document the autoDeploy setting, HelmChart weights, operator-upgrade behavior, listed edge cases, and channel recommendations in applications/mlflow/docs/auto-update.md, then link it from the README.