Consider build-time warnings for dependency policy and outdated modules

[MariusStorhaug]

Context

When building modules in this repository, we should consider warning users/maintainers when dependencies appear risky or stale.

Areas to evaluate

1. Poorly written dependency rules
   • Example concern: version constraints that are too strict or otherwise brittle.
   • Should we prefer locking to major versions as a safer default strategy?
2. Outdated modules
   • Warn when a dependency is clearly out of date.
   • Define what "outdated" means (latest stable? outside supported window?).

Questions to decide

• Where in the build pipeline should warnings be emitted?
• What rules are warning-only vs. blocking?
• How configurable should this be (repo defaults vs. per-module overrides)?
• What should warning messages include to be actionable?

Suggested outcome

• Agreed warning policy and heuristics for dependency constraints and outdated modules.
• Implementation plan for Process-PSModule (and any shared logic if needed).