feat: add min-release-age-exclude with glob pattern support

[caseyjhol]

Summary

• add a new npm config option, min-release-age-exclude, to exclude selected packages from before / min-release-age publish-time filtering
• support both exact package names and glob patterns (for example @myorg/*)
• apply the exclusion behavior consistently across manifest picking and query/outdated logic, with tests and snapshot updates

Motivation

min-release-age is useful for supply-chain risk reduction, but teams often need fast updates for internal packages or urgent CVE responses. This adds an exclusion mechanism so strict age policies can coexist with targeted exceptions.

Changes

• config definition + flattening to flatOptions.minReleaseAgeExclude
• glob matching for excluded package names in publish-time filtering
• consistent behavior in arborist query/outdated paths
• tests for config flattening and exclusion behavior (exact + glob)
• docs/snapshot updates for the new option

Test plan

• run focused config tests for min-release-age-exclude flattening
• run arborist query selector tests covering before + exclusion behavior
• refresh docs snapshots and verify generated help/config output updates

Related issues

• Closes npm/cli#8994
• Also addresses related request in npm/cli#8979 comment