📖 [Docs]: Guide major-version bounding for #Requires module dependencies

[Marius Storhaug (MariusStorhaug)]

The PowerShell scripts coding standard now explains how to version-constrain #Requires module dependencies, so authors pick the pin that matches their risk appetite instead of making ad-hoc choices.

Changed: #Requires version-constraint guidance

The Scripts standard now recommends a minimum version by default, a major-version bound (MaximumVersion = 'N.*') for dependencies whose new major would break you — a test framework like Pester being the typical case — and avoiding exact RequiredVersion pins that freeze out patches. Module-identity pinning with a GUID is called out as a separate, stricter supply-chain control, used only when identity assurance is needed and not as part of the default version lock.

Technical Details

• Updates src/docs/Coding-Standards/PowerShell/Scripts.md (the #Requires item in the section structure and the example).
• Aligns with the Pester 6.x lock adopted across the PSModule modules (Dependency management for PowerShell scripts and modules PSModule/Process-PSModule#356).