fix(ci): ansible-lint job use pinned ansible-core 2.18 + galaxy install

Drop ansible-lint action uv stack (latest ansible-core breaks Galaxy install).
Install ansible-lint with ansible-core<2.19, pre-install requirements.yml
collections, then lint. Revert .ansible-lint offline so modules resolve.

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: Martin Jackson

.ansible-lint

@@ -1,9 +1,6 @@
 # Vim filetype=yaml
 ---
-# Skip ansible-galaxy collection install from requirements.yml. Recent ansible-core
-# releases can hit Galaxy API KeyError: 'results' during install (CI and local uv).
-# Install collections manually or use creator-ee when you need dependency-aware rules.
-offline: true
+offline: false
 skip_list:
   - name[template] # Allow Jinja templating inside task and play names
   - template-instead-of-copy # Templated files should use template instead of copy

.github/workflows/ansible-lint.yml

@@ -14,7 +14,21 @@ jobs:
         with:
           persist-credentials: false
 
-      - name: Lint Ansible Playbook
-        uses: ansible/ansible-lint@5fac056c45595896c973fbde871f01f6cb14d74c
+      # The ansible-lint GitHub action installs via uv with a lock that tracks the newest
+      # ansible-core; ansible-galaxy collection install then hits Galaxy KeyError: 'results'
+      # on some 2.19+/2.20 clients. Pin ansible-core to the 2.18 series for a stable Galaxy client.
+      - name: Set up Python
+        uses: actions/setup-python@v5
         with:
-          setup_python: "true"
+          python-version: "3.12"
+
+      - name: Install ansible-lint and Galaxy-compatible ansible-core
+        run: |
+          python -m pip install --upgrade pip
+          pip install ansible-lint "ansible-core>=2.18.0,<2.19.0"
+
+      - name: Install Ansible Galaxy collection dependencies
+        run: ansible-galaxy collection install -r requirements.yml
+
+      - name: Run ansible-lint
+        run: ansible-lint roles playbooks plugins