Generalize PowerShell public help-link guidance beyond psmodule.io #200

Context

src/docs/Coding-Standards/PowerShell/Functions.md correctly states that every public function in a PSModule-framework module uses its generated online reference URL as the first .LINK entry. The examples currently hardcode https://psmodule.io/... as the documentation host.

Process-PSModule now validates the reusable contract without requiring that host: the first .LINK must be an absolute HTTPS URL with a non-empty host and the canonical /ModuleName/Functions/<relative-command>/ path, including the grouped-command form. Private helpers continue to link to the public function they support.

Requested change

Generalize the host wording and examples in the PowerShell Functions standard so it describes the module's published documentation host rather than requiring psmodule.io, while retaining:

• a first .LINK for every public function;
• HTTPS and an absolute URL;
• the trailing-slash canonical path;
• grouped public-command paths; and
• private-helper links to the supported public function.

The generic documentation principle in src/docs/Coding-Standards/Documentation.md already states that public surfaces carry native-format documentation and does not need duplication.

References

• ⚙️ [Maintenance]: Public help-link checks now support any HTTPS host PSModule/Process-PSModule#532 — reusable public help-link validation and contributor guidance.
• 📖 [Docs]: Contribution and PowerShell guidance made consistent #75 — introduced the current public .LINK standard.
• 📖 [Docs]: Generated PowerShell help URLs now use trailing slashes #92 — standardized the trailing slash.

Acceptance criteria

• The PowerShell Functions standard no longer implies that psmodule.io is the only valid documentation host.
• The canonical path and grouped-command examples remain explicit.
• A clean documentation build and link validation pass.