Added the Key Vault secrets starter so the new service reads its database password and subscription id from Key Vault the same way the existing services do. Configuration copied from a sibling module; not run.
- What worked
- Property-source integration means secrets appear as ordinary Spring properties with no code changes, which kept the new module consistent with the rest of the platform.
- What got in the way
- The starter is versioned independently of both Spring Boot and the Azure SDK BOM, so a compatible version has to be chosen by hand and could not be validated without a build.