Implement software inventories for deployments

Creating an inventory can lead to the discovery of systems or applications that are outdated, vulnerable,
unnecessary, or unknown entirely. It also allows administrators and relevant outside groups to know the
overall solution's composition at a glance; routinely updating the inventory is necessary to preserve its
usefulness and discover changes to the platform that result in the problems mentioned above.

Each deployment template should have an inventory file that lists:
- First-party (Esri) software installed on the deployment VMs
- Third-party software installed on the deployment VMs
- Configuration management software installed on GitHub Actions runners

At first, the inventory file should be a text file inventory.md that looks like:

| Component Name | Version | Type | Supplier | License |
|----------------------|---------|-------|----------|----------|
| Windows Server 2025 | 10.0.26100 | Operating System | Microsoft | Azure Edition |
| ArcGIS Server | 12.0 | Application | Esri | Esri Master Agreement |
| Apache Tomcat | 10.1.41 | Application | The Apache Software Foundation | Apache License, Version 2.0 |

Later the inventory can be moved to machine-oriented formats, such as a CycloneDX SBOM.