Publish docs when layout/config files change in PRs

[MariusStorhaug]

Summary

When a pull request changes docs site layout/configuration files (for example .github/zensical.toml), Process-PSModule should publish a new docs version to GitHub Pages, even when markdown content itself is unchanged.

Problem

Today, docs publishing appears to be primarily content-driven. Layout/config-only updates can merge without triggering a docs publish, leaving GitHub Pages out of sync with the repository.

Proposal

Add a docs-publish trigger path/classification for site-structure and theme/config changes, including (at minimum):

• .github/zensical.toml
• docs theme overrides/assets/config files used by the site generator
• navigation/layout-specific config files (not only markdown content)

Expected behavior

If a PR includes one of those layout/config changes, Process-PSModule should run the docs publish path and deploy updated GitHub Pages output.

Acceptance criteria

1. A PR that changes only .github/zensical.toml triggers docs publish.
2. A PR that changes only a layout/theme asset used by docs triggers docs publish.
3. A PR with no docs-related changes does not trigger docs publish solely because of this rule.
4. Existing content-change publish behavior remains intact.

Context

This came up while updating Sodium docs config: visual/layout changes were needed, and those should be reflected on Pages immediately after merge.