Refresh aggregate SD-WAN automation stack

[sashiv20]

Summary

• Target Ansible 14.3.1 / ansible-core 2.21.3 on Python 3.12-3.14.
• Update aggregate dependency floors to current published Cisco child collections, amazon.aws 11.4.0, and azure.azcollection 3.21.0.
• Replace the obsolete no-dependency installation workaround with normal resolver-based installation and current Azure provider dependency guidance.
• Refresh requirements CI across Python 3.12-3.14, release/importer actions, maintenance hooks, and artifact exclusions.
• Bump the aggregate collection to 0.3.7.

Coordinated child PRs

• cisco.catalystwan: Refresh Catalyst SD-WAN compatibility for current releases ansible-collection-catalystwan#67
• cisco.sdwan_deployment: Refresh AWS and Azure deployment compatibility ansible-collection-sdwan-deployment#58

The child PRs contain the Manager/SDK and cloud-provider compatibility work. Merge and live-validate those first. Their new collection versions should be published before the aggregate 0.3.7 release; the aggregate dependency floors can then be raised to those newly published versions if maintainers want to require the maintenance fixes rather than preserve the current compatibility floor.

Why

The aggregate collection was pinned to obsolete Ansible, Python, catalystwan, AWS, and Azure dependency guidance. It also instructed users to bypass pip dependency resolution for a historical catalystwan 0.31.2 / azure-cli-core 2.34.0 conflict that no longer applies.

This update makes the installation path resolver-safe and aligns CI and release packaging with the maintained child collections.

Validation

• pre-commit 4.6.2: all changed-file hooks passed
• ansible-lint production profile: passed
• collection build succeeded as cisco.sdwan 0.3.7
• built artifact installed successfully alongside the child collection artifacts
• artifact inspection confirmed CI/cache/bytecode/prior-tarball content is excluded

Final validation

• All 8 hosted checks pass on commit c881b75, including Python 3.12-3.14 sanity, dependency installation, static analysis, and Galaxy importer validation.
• The coordinated Catalyst WAN and deployment PRs completed their live Manager and cloud lifecycle validation and are ready for review.
• Release ordering remains: publish the child collection versions first, then publish the aggregate collection.
• A fresh pip-audit of the 54-package resolved PR environment reported no known vulnerabilities.