[AVM CI Environment Issue]: Mandate and update all custom types with external relevance to use the `@export()` annotation

[AlexanderSehr]

Check for previous/existing GitHub issues

• [X] I have checked for previous/existing GitHub issues

Issue Type?

Feature Request

Description

This issue is based on this proposal.

The idea:

• Update both the AVM specs & modules to add the @export() annotation to their types (if they should be 'importable')
• This would allow anybody using the modules to also important any custom type and re-use it when defining their own interface that uses the module
• We already do this today in a few cases where parent modules reference exported types of their child modules. This approach would just go a bit further as you could also import the type directly from the Public Bicep Registry. https://github.com/Azure/bicep-registry-modules/blob/34c5bf10c4cb75fbd51db3fd4a030a7cb6d6bd7b/avm/res/compute/gallery/main.bicep#L251

This should be done for both the top-level modules, as well as the child-modules. The later won't be available for import just yet, but once we finally manage to find a scalable way to publish child-modules, they would automatically become available too.

[microsoft-github-policy-service[bot]]

[!IMPORTANT] The "Needs: Triage :mag:" label must be removed once the triage process is complete!

[!TIP] For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

[microsoft-github-policy-service[bot]]

[!WARNING] Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

[!TIP]

• To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
• To avoid this rule being (re)triggered, the ""Needs: Triage :mag:" label must be removed as part of the triage process (when the issue is first responded to)!

[microsoft-github-policy-service[bot]]

[!WARNING] Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

[!TIP]

• To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
• To avoid this rule being (re)triggered, the ""Needs: Triage :mag:" label must be removed as part of the triage process (when the issue is first responded to)!

[microsoft-github-policy-service[bot]]

[!CAUTION] This issue requires the AVM Core Team's (@Azure/avm-core-team-technical-bicep) immediate attention as it hasn't been responded to within 6 business days.

[!TIP]

• To avoid this rule being (re)triggered, the "Needs: Triage :mag:" and "Status: Response Overdue :triangular_flag_on_post:" labels must be removed when the issue is first responded to!
• Remove the "Needs: Immediate Attention :bangbang:" label once the issue has been responded to.