feat(pnpm-policy): default the wait to two days

[pyramation]

Summary

-export const DEFAULT_MINIMUM_RELEASE_AGE = '14d';
+export const DEFAULT_MINIMUM_RELEASE_AGE = '2d';

Two weeks was the wrong tradeoff to ship as a default. A compromised release — hijacked account, typosquat, malicious postinstall — is normally reported and yanked within hours, so almost everything a cooldown buys you lands in the first day or two; the remaining twelve days mostly buy the sensation of security while making every legitimate upgrade feel like it needs a waiver. A default people route around is worth less than a shorter one they leave on.

Also flows through pnpm-policy init's starter config, the README's config table and examples, and @constructive-io/pnpm-policy's own pnpm-policy.yaml (the data package our repos pin). Consuming repos set the value explicitly, so this only reaches them if they follow — constructive and constructive-db do, in their own PRs.

Link to Devin session: https://app.devin.ai/sessions/ffa3b012deac4eb7afb8f49a9af9f9ca
Requested by: @pyramation

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring