Add devcontainer configuration for Codespaces

[Copilot]

Summary

Adds a .devcontainer/devcontainer.json so the repository can be opened in GitHub Codespaces or any other devcontainer-compatible tool (VS Code Dev Containers, JetBrains, etc.) with a ready-to-use Ansible development environment.

Changes

• New file: .devcontainer/devcontainer.json
  • Base image: mcr.microsoft.com/devcontainers/python:1-3.12-bookworm (Python is the runtime for Ansible).
  • Features: common-utils, git, github-cli.
  • postCreateCommand: installs ansible, ansible-lint, yamllint, and the collections from requirements.yaml via ansible-galaxy collection install -r requirements.yaml, matching what the CI workflow expects.
  • VS Code customizations: recommends the Red Hat Ansible & YAML extensions, GitHub Actions extension, and Python extension; enables ansible-lint validation. The Red Hat Ansible extension auto-detects Ansible files via its built-in patterns, so no global *.yaml/*.yml → ansible association is set — this preserves GitHub Actions schema/validation for files under .github/workflows/.

Usage

After merging, contributors can:

• Click Code → Codespaces → Create codespace on GitHub, or
• Run Dev Containers: Reopen in Container in VS Code locally.

The container will come up with ansible-playbook, ansible-lint, and yamllint available, and all required collections preinstalled — so the same lint/build commands used by .github/workflows/ansible-ci.yml work out of the box.

[Copilot]

Pull request overview

Adds a devcontainer definition so contributors can open this Ansible infrastructure repo in Codespaces/devcontainer tools with a preconfigured development environment.

Changes:

• Adds a new .devcontainer/devcontainer.json based on the Python devcontainer image.
• Installs Ansible, ansible-lint, yamllint, and the repo’s required Ansible collections after container creation.
• Configures recommended VS Code extensions and editor settings for Ansible/YAML work.

[tormachris]

@copilot apply changes based on the comments in this thread

[Copilot]

@copilot apply changes based on the comments in this thread

Removed the global *.yaml/*.yml → ansible file association in 59bcc9c so GitHub Actions workflow files keep their schema/validation. The Red Hat Ansible extension auto-detects Ansible files (playbooks, roles/*/tasks/*.yml, etc.) without needing the blanket association.