Release: CNAME fix for www.conduction.nl + accumulated dev

[rubenvdlinde]

Summary

• Brings static/CNAME fix from fix: set Pages CNAME to www.conduction.nl #12 onto main so Deploy to GitHub Pages runs with the correct CNAME (www.conduction.nl).
• Also includes any accumulated commits on development since main last shipped (yesterday).

Without this merge the Pages artifact keeps shipping CNAME=docs.conduction.nl, which prevents Let's Encrypt cert issuance for www.conduction.nl.

Test plan

• After merge, Deploy to GitHub Pages workflow run on main succeeds
• gh api repos/ConductionNL/conduction-website/pages shows https_certificate.state == "approved" for www.conduction.nl
• https://www.conduction.nl/ returns 200 with valid TLS cert

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.