Verify canary release

• I verified that the issue exists in the latest Turborepo canary release.

Describe the Bug

╭──────────────────────────────────────────────────────────────────────╮
│                                                                      │
│                   Update available v2.0.3 ≫ v2.0.4                   │
│    Changelog: https://github.com/vercel/turbo/releases/tag/v2.0.4    │
│           Run "npx @turbo/codemod@latest update" to update           │
│                                                                      │
│        Follow @turborepo for updates: https://x.com/turborepo        │
╰──────────────────────────────────────────────────────────────────────╯

Expected Behavior

Feature Request

I want to be able to configure turbo.json as follows:

{
  "meta": {
    "disableUpdateChecks": true
  }
}

If I opt-in to this setting, then Turbo will not check to see if there is a new version.

Why?

Every tool and every library seems to have its own update checks these days. The DX is, log in for the day, start working, see which tool I need to update today. Either I stop what I'm doing to install the update, which is exhausting over a long period of time, or I mentally check out and ignore the version update notice, which defeats the purpose.

To keep my dependencies (including Turbo) up-to-date, I use Renovate Mend (there are alternatives like GitHub's Dependabot), which allows me to not just isolate dependency updates to their own PRs but also to keep these dependency updates restricted to a schedule. Instead of being pressured to update something every day, I can say OK I'll do dependency updates once a week, once every two weeks, once a month, and have the mental space to work on feature development most days.

As a user with automated dependency updating set up, I would like to disable Turbo's built-in update version checking.