📖 [Docs]: PowerShell module dependency guidance clarified

[Marius Storhaug (MariusStorhaug)]

PowerShell module authors are now guided to prefer PowerShell, the .NET base class library, and code we own before introducing third-party modules, DLLs, or packages. The dependency guidance now treats a new external dependency as an explicit tradeoff instead of the default path.

Changed: PowerShell module dependency guidance

The general dependency standard, the PowerShell coding standard, the function reuse guidance, and the Process-PSModule repository guidance now consistently say that shipped modules should avoid third-party dependencies when the capability can reasonably be implemented with platform primitives or owned code. This keeps the maintenance surface, trust boundary, and long-term update burden clearer for module authors.

Technical Details

• Added the dependency-avoidance guidance to src/docs/Coding-Standards/Dependencies.md.
• Updated src/docs/Coding-Standards/Functions.md and src/docs/Coding-Standards/PowerShell/index.md to prefer owned code before third-party dependencies.
• Updated src/docs/Frameworks/Process-PSModule/repository-structure.md so #Requires -Modules is framed as the path for genuinely necessary external modules.