[Bicep Child Module Proposal]: `dot-net-component`

### 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 for 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?

I want to implement the functionality AND make it available as a published child module

### Parent module?

avm/res/app/managed-environment

### Module Name

dot-net-component

### Module Details

This module deploys an App Managed Environment .NET Component.This child module deploys a Microsoft.App/managedEnvironments/dotNetComponents resource under the managed-environment parent module. It supports the componentType, configurations, and serviceBinds properties, enabling deployment of .NET Aspire components (e.g., Aspire Dashboard) into a Container Apps managed environment.

Start with the avm/res/app/managed-environment parent module and review the linked pull request for the proposed dot-net-component implementation. Confirm that the child module targets Microsoft.App/managedEnvironments/dotNetComponents and supports componentType, configurations, and serviceBinds, then verify that it is available as a published child module.

Written by the indexing model from the issue text.