The processes described in the Module Support page and Module Lifecycle do not seem to be followed

### Check for previous/existing GitHub issues

- [x] I have checked for previous/existing GitHub issues

### Description

The processes (and timelines) described in

- the Module Support page and
- the Module Lifecycle page

do not seem to be followed (for Terraform, at least).

For example, the App Gateway module has issues opened since November that have not even been triaged.
But the module is not indicated as orphaned either. https://github.com/Azure/terraform-azurerm-avm-res-network-applicationgateway/issues.

I think the AVM is a great initiative from Microsoft but if it is advertised as supported by Microsoft, it should be actively supported. This makes it harder to recommend using these modules to customers.

Start by reading the Module Support page and Module Lifecycle page, then compare their stated processes and timelines with the App Gateway module's open issues. Check whether the pages or the support process is the source of the discrepancy, and define an agreed resolution for the documented expectations and module status.

Written by the indexing model from the issue text.