Fix Palace availability in CI documentation builds using Apptainer containers

[Copilot]

This PR resolves the issue where Palace simulations fail during documentation builds in CI due to Palace not being available in the build environment.

Problem

Documentation builds were failing with errors like:

RuntimeError: palace not found. Make sure it is available in your PATH or via Spack.

This occurred because the pages.yml workflow for building docs didn't include Palace setup, while the test_palace job in test_code.yml successfully uses Apptainer containers.

Solution

1. Enhanced Palace Detection

• Created gplugins/palace/utils.py with robust Palace executable detection
• Supports multiple installation methods: PATH → Apptainer/Singularity containers → Spack fallback
• Automatically detects CI environments and container runtimes
• Generates execution scripts for containerized Palace

2. Updated Palace Execution

• Modified get_capacitance.py and get_scattering.py to use the new detection utility
• Maintains backward compatibility with existing Spack and PATH installations
• Provides consistent error messaging across modules

3. Enhanced Documentation CI

• Updated pages.yml workflow to include Palace container setup matching test_palace job
• Implements identical caching strategy for efficient container reuse
• Added graceful fallback when container builds fail or timeout
• Conditional Palace setup with proper error handling

Key Features

• Container Cache Reuse: Uses same cache key as test_palace job for efficient builds
• Graceful Degradation: Clear error messages when Palace unavailable, no silent failures
• Multi-Runtime Support: Works with both apptainer and singularity
• Backward Compatible: Existing Palace installations continue working unchanged
• CI-Optimized: Automatic detection of GitHub Actions environment

Testing

Palace notebooks in documentation will now execute successfully when Apptainer containers are available, with efficient cache sharing between test and documentation workflows.

Fixes #651.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• astral.sh
  • Triggering command: curl -LsSf REDACTED (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[sourcery-ai]

New security issues found

[joamatab]

@nikosavola there seems to be a conflict

Already considered