[Bicep Child Module Proposal]: `avm/res/sql/managed-instance` child modules

## Check for previous/existing GitHub issues/module proposals - [x] I have checked for previous/existing GitHub issues/module proposals. ## Check this module doesn't already exist in the module indexes - [x] I have checked that this module doesn't already exist in the module indexes. ## Do you want to add new functionality to an existing module, publish an existing child module or both? The functionality exists already and I want to make it available as a published child module independent from its parent module. ## Parent module `avm/res/sql/managed-instance` ## Module Name This proposal covers publishing **all 7 existing child modules** under `avm/res/sql/managed-instance` as independently-published modules in the public Bicep registry: | # | Child module | Telemetry ID prefix | | - | ------------ | ------------------- | | 1 | `avm/res/sql/managed-instance/database` | `46d3xbcp.res.sql-mi-database` | | 2 | `avm/res/sql/managed-instance/database/backup-long-term-retention-policy` | `46d3xbcp.res.sql-mi-dbbckplongermretpolicy` | | 3 | `avm/res/sql/managed-instance/database/backup-short-term-retention-policy` | `46d3xbcp.res.sql-mi-dbbckpshortermretpolicy` | | 4 | `avm/res/sql/managed-instance/encryption-protector` | `46d3xbcp.res.sql-mi-encryptionprotecor` | | 5 | `avm/res/sql/managed-instance/key` | `46d3xbcp.res.sql-mi-key` | | 6 | `avm/res/sql/managed-instance/security-alert-policy` | `46d3xbcp.res.sql-mi-securityalertpolicy` | | 7 | `avm/res/sql/managed-instance/vulnerability-assessment` | `46d3xbcp.res.sql-mi-vulnerabilityassessment` | ## Module Details These child modules already exist in the [BRM source code](https://github.com/Azure/bicep-registry-modules/tree/main/avm/res/sql/managed-instance) and are referenced from the parent `avm/res/sql/managed-instance` module today. This proposal makes them independently consumable from the public registry so that solutions and pattern modules can reference them directly without going through the top-level managed instance module. ### Prerequisite checklist - ✅ Telemetry ID prefixes assigned in the [Bicep Resource Modules CSV](https://github.com/Azure/Azure-Verified-Modules/blob/main/docs/static/module-indexes/BicepResourceModules.csv). - ✅ Modules registered in the [MAR file](https://github.com/microsoft/mcr/blob/main/teams/bicep/bicep.yml). - ✅ Parent module `avm/res/sql/managed-instance` is in `Available` status with assigned owner (`@chanakanissanka`). ### Implementation Implementation PR: _to be linked once the BRM PR is filed._ Each child module `main.bicep` was instrumented with the AVM `enableTelemetry` parameter and `avmTelemetry` deployment per [SFR4](https://azure.github.io/Azure-Verified-Modules/spec/SFR4)/[SFR3](https://azure.github.io/Azure-Verified-Modules/spec/SFR3)/[BCPFR4](https://azure.github.io/Azure-Verified-Modules/spec/BCPFR4). The parent module(s) — `avm/res/sql/managed-instance` and `avm/res/sql/managed-instance/database` — were updated with the `enableReferencedModulesTelemetry` variable and pass-through to child invocations per [BCPFR7](https://azure.github.io/Azure-Verified-Modules/spec/BCPFR7). Each new published module has a `version.json` (`0.1`) and an initial `CHANGELOG.md` (`0.1.0`). The parent's CHANGELOG is bumped to `0.4.1` listing all 7 published children. > **NOTE**: > > - This Module Proposal issue **MUST remain open** until the modules are fully developed, tested and published to the public Bicep registry. > - Once successfully published and the issue is closed, it **MUST remain closed**.