fix: take our own releases past Dependabot's three-day wait
Closes #19.
Dependabot holds new versions back three days and runs pnpm with --config.minimum-release-age=4320, and pnpm then refuses every locked version younger than that. This site pins @missing-elements releases as they come out, so the next weekly npm run, due about 2026-11-12, would fail on h5p-author 0.6.0, locked 2026-11-09. The org site's daily job already does (missing-elements/missing-elements.github.io#9, fixed the same way in #10).
pnpm-workspace.yaml(new, settings only):minimumReleaseAgeExclude: ["@missing-elements/*"]..github/dependabot.yml:cooldownkeeps the three days for every other package and excludes ours, so a release of ours gets its PR at the next weekly run rather than three days later.
Checked locally with Dependabot's own command, pnpm update @playwright/test --lockfile-only --config.minimum-release-age=…. Without the file it fails on h5p-author 0.6.0; with it, it passes, at the full three days too. pnpm install --frozen-lockfile is unchanged.
Summary by cubic
Dependabot's three-day wait on new versions made pnpm refuse @missing-elements packages locked within the last three days, so weekly npm runs could fail. The new pnpm-workspace.yaml excludes those packages from pnpm's minimum-release-age check, and Dependabot's cooldown now excludes them too; every other package keeps the three-day wait.