revert to use withoutConcurrentExecution

[conico974]

This PR reintroduce withoutConcurrentExecution, because on some big page like the MariaDB one, it will just crash. In order to avoid the previous issue on vercel, we use React.cache({})` as our global request context so that it doesn't leak to other request with fluid compute.

It also disable resolvingAnchorText on InlineLink because with it, the request will just timeout if there is too many of them in a single page

[linear]

RND-7263 Large MariaDB page not loading (GBO V2 on Vercel)

[github-actions]

Summary of the deployments:

Version 1

Version	URL	Status
Latest commit	https://189a5a48.gitbook-open.pages.dev	✅
PR	https://pr3292.gitbook-open.pages.dev	✅

Version 2

Version	URL	Status
Vercel	https://gitbook-v2-ap14p7zok-gitbook.vercel.app	✅
Cloudflare	https://5237dfe8-gitbook-open-v2-preview.gitbook.workers.dev	✅

Test content

Site	v1	2v	2c
GitBook	https://189a5a48.gitbook-open.pages.dev/gitbook.com/docs	https://gitbook-v2-ap14p7zok-gitbook.vercel.app/url/gitbook.com/docs	https://5237dfe8-gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs
E2E	https://189a5a48.gitbook-open.pages.dev/gitbook.gitbook.io/test-gitbook-open	https://gitbook-v2-ap14p7zok-gitbook.vercel.app/url/gitbook.gitbook.io/test-gitbook-open	https://5237dfe8-gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.gitbook.io/test-gitbook-open

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
customers-v1 (Inspect)	👍 Changes approved	22 changed, 4 removed	Jun 10, 2025, 4:37 PM
customers-v2 (Inspect)	👍 Changes approved	22 changed, 4 removed	Jun 10, 2025, 4:53 PM
default (Inspect)	👍 Changes approved	14 changed	Jun 10, 2025, 4:41 PM
v2-cloudflare (Inspect)	👍 Changes approved	14 changed	Jun 10, 2025, 4:56 PM
v2-vercel (Inspect)	👍 Changes approved	14 changed	Jun 10, 2025, 4:55 PM

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0096568

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[SamyPesse]

Looks good, but when I think about it, we might still need to manage concurrency inside the use cache: imagine that the Node.js process receive 10 requests to generate pages in the same space, right now it'll result in 10 API requests to the same space for each of the top level requests.
I think we should manage concurrency at 2 levels:

• Wrapping in the use cache: per-request using cache(() => {})
• Wrapping the API call in the use cache: global in the process