Disable Dependabot during closed development

[ufukty]

Context

• This issue exists solely to document the decision and impact for future reference. As of writing, I have already disabled Dependabot and closed all pending PRs.
• Dependabot had a number of open PRs:
  • build(deps): bump cryptography from 44.0.1 to 48.0.1 in /dev #71
  • build(deps-dev): bump vite from 7.1.12 to 7.3.5 in /backend/cmd/auth/web/ts #70
  • build(deps): bump esbuild and vitest in /backend/cmd/auth/web/ts #69
  • build(deps-dev): bump vitest from 3.2.3 to 3.2.6 in /backend/cmd/auth/web/ts #58
  • build(deps-dev): bump vite from 7.1.12 to 7.3.3 in /backend/cmd/auth/web/ts #47
  • build(deps-dev): bump postcss from 8.5.6 to 8.5.15 in /backend/cmd/auth/web/ts #46
  • build(deps-dev): bump happy-dom from 20.0.2 to 20.9.0 in /backend/cmd/auth/web/ts #45
  • build(deps): bump cryptography from 44.0.1 to 46.0.6 in /dev #39
  • build(deps-dev): bump picomatch from 4.0.3 to 4.0.4 in /backend/cmd/auth/web/ts #37
  • build(deps-dev): bump rollup from 4.52.5 to 4.59.0 in /backend/cmd/auth/web/ts #35
• Dependabot bumps a dependency's version on a recurring schedule, and each bump requires some review time.
• During pre-release, closed-stage development, resolving these Dependabot PRs serve no purpose, since they are superseded by newer ones before they face users.

Problem

Maintaining operations-only concerns during closed development adds friction without delivering value.

Suggestion

Disable Dependabot during closed development.