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

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
(PSModule/Process-PSModule#356).

Author: MariusStorhaug

src/docs/Coding-Standards/PowerShell/Scripts.md

@@ -11,15 +11,15 @@ A script (`.ps1`) is an entry point, not a home for logic. Keep scripts **thin**
 
 A script file is laid out top to bottom in this order:
 
-1. **`#Requires`** statements — PowerShell version and module dependencies with minimum versions.
+1. **`#Requires`** statements — PowerShell version and module dependencies. Prefer a **minimum** version (`ModuleVersion`) so security patches and fixes flow in. When a new *major* of a dependency would break you — a test framework such as Pester is the typical case — bound it to that major by adding `MaximumVersion` (e.g. `ModuleVersion = '6.0.0'; MaximumVersion = '6.*'`). Avoid exact `RequiredVersion` pins, which freeze out patches and go stale. Pinning module identity with a `GUID` is a separate, stricter supply-chain control — reach for it only when you need identity assurance, not as part of the default version lock.
 2. **Comment-based help** — the same sections and order as a [function's](Functions.md#comment-based-help-required), only without the enclosing `function` block: `.SYNOPSIS`, `.DESCRIPTION`, at least one `.EXAMPLE`, then `.INPUTS`, `.OUTPUTS`, `.NOTES`, and `.LINK` as they apply. Document each parameter with an inline comment above it, just as a function does.
 3. **`[CmdletBinding()]` + `param()`** — typed and validated, mandatory first; add `SupportsShouldProcess` when the script changes state.
 4. **`$ErrorActionPreference = 'Stop'`**.
 5. **Body** — the thin orchestration.
 
 ```powershell
 #Requires -Version 7.0
-#Requires -Modules Pester
+#Requires -Modules @{ ModuleName = 'Pester'; ModuleVersion = '6.0.0'; MaximumVersion = '6.*' }
 
 <#
     .SYNOPSIS