Fix offline install missing community.general collection

[ssimpson89]

Summary

• The offline collection install block in setup.sh was missing community.general
• This collection is required by the assertions playbook (community.general.collection_version lookup)
• On offline RKE2 installs, setup.sh fails immediately with lookup plugin (community.general.collection_version) not found
• The collection tarball is already downloaded by create_bundle.yml into offline/collections/ but was never installed by setup.sh

Test plan

• Run setup.sh with k8s_offline: true and k8s_platform: rke2
• Verify assertions playbook passes without the collection_version lookup error
• Verify online installs are unaffected (online path uses requirements.yml which already includes community.general)

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR addresses failures in offline installs by ensuring the community.general Ansible collection (needed for the community.general.collection_version lookup used in playbooks/assertions.yml) is installed by setup.sh when using the offline collections bundle.

Changes:

• Add community.general tarball installation to the offline collections install block in setup.sh.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The offline install branch still only installs a subset of the collections that are bundled from collections/requirements.yml. Since playbooks/setup.yml always imports playbooks/assertions.yml and required_collections includes azure.azcollection and google.cloud, offline runs can still fail collection assertions even with community.general installed. Consider installing all bundled collection tarballs (or otherwise ensuring the full required_collections set is installed) in the offline path.

[Copilot]

This new community.general install line may never run in environments where the other checked collections are present but community.general is missing, because check_collections() doesn’t currently verify any community.general plugin/module. Consider updating the detection logic to include a check for the community.general.collection_version lookup (or another community.general component), so missing community.general reliably triggers the install block.

[Copilot]

The offline collection install commands use an unquoted $(dirname $0) path. If the script path contains spaces or glob characters, this will break and can cause ansible-galaxy to receive a truncated path. Quote the dirname expansion (and ideally compute a SCRIPT_DIR once) before building these file paths.