[Feature Request]: Manage resource API versions for dependencies and existing resources

### Description

The CI environment is currently monitoring module API versions for primary resources through Pester and the AzureAPICrawler utility.

Discuss if worthy and how to monitor API versions used to deploy test dependencies and other resources not monitored by the static validation tests.

A possibility could be to implement a scheduled platform pipeline (e.g. weekly), checking the whole library in audit mode, leveraging the AzureAPICrawler utility to provide a report of which versions are used for each resource type and if they are stale wrt the latest available ones.