refactor(cache): deprecate global disableDynamoDBCache and disableIncrementalCache

[vicb]

@conico974 Actually, this might be a breaking change...
So maybe I should deprecate instead and add a changeset then we can remove later.
WDYT?

[changeset-bot]

🦋 Changeset detected

Latest commit: 6a5f350

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
@opennextjs/aws	Patch
app-pages-router	Patch
app-router	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	23.45%	1878 / 8006
🔵	Statements	23.45%	1878 / 8006
🔵	Functions	56.41%	110 / 195
🔵	Branches	70.72%	471 / 666

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
packages/open-next/src/adapters/cache.ts	86.66%	83%	100%	86.66%	93-94, 155-157, 160-168, 216-227, 379-388, 423-431, 465-466
packages/open-next/src/overrides/tagCache/dynamodb-lite.ts	0%	0%	0%	0%	1-220
packages/open-next/src/overrides/tagCache/dynamodb.ts	0%	0%	0%	0%	1-166
packages/open-next/src/types/global.ts	0%	0%	0%	0%

Generated in workflow #894 for commit 6a5f350 by the Vitest Coverage Report Action

[pkg-pr-new]

Open in Stackblitz

pnpm add https://pkg.pr.new/@opennextjs/aws@702

commit: 6a5f350

[conico974]

This is kind of a breaking change, some people may rely on it (especially if they have a custom tag cache that they reuse across multiple apps).
Fully removing this in a future minor (with a warning) is probably more than enough, there is likely very very few people that rely on this ( if any at all )

[conico974]

LGTM Thanks

[vicb]

Thanks for the review