Align module documentation publishing

[lipkau]

Summary

• publish JiraAgilePS in the website module navigation
• document the release-aligned module submodule policy
• add a Pages guardrail that checks active module submodules against release tags or explicit docs-only exceptions
• mark active and legacy module metadata consistently
• route About group navigation to the module root so about_<Module>.md remains the canonical landing page

Validation

• bash .github/scripts/check-module-submodules.sh
• Ruby YAML parse for _data/navigation.yml, _data/modules.yml, _data/index/modules.yml
• bundle exec jekyll build

Notes

• JiraAgilePS is treated as the current no-tags baseline because the repository has no remote tags or GitHub releases.
• AtlassianPS.Configuration commit 555e8a3300a12e03b1d9c494a874fe21fe9bbccf is allowed as a narrow docs-only exception.
• This PR includes the earlier JiraAgilePS submodule update plus the website publishing policy and guardrail.