Fix hydration error on V2

[conico974]

Inserting an inline link inside a card would cause an <a> tag to be nested inside another <a> tag.
This cause an hydration error in GBO v2, and initial render from the server would not render properly and the card would only appear after client hydration.

[linear]

RND-7231 Nested `<a>`cause hydration errors on GBO

[changeset-bot]

🦋 Changeset detected

Latest commit: a4430fa

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

This PR includes changesets to release 1 package

Name	Type
gitbook	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]

Summary of the deployments:

Version 1

Version	URL	Status
Latest commit	https://b4c3d85c.gitbook-open.pages.dev	✅
PR	https://pr3272.gitbook-open.pages.dev	✅

Version 2

Version	URL	Status
Vercel	https://gitbook-v2-iyjtw9ekt-gitbook.vercel.app	✅
Cloudflare	https://8691b741-gitbook-open-v2-preview.gitbook.workers.dev	✅

Test content

Site	v1	2v	2c
GitBook	https://b4c3d85c.gitbook-open.pages.dev/gitbook.com/docs	https://gitbook-v2-iyjtw9ekt-gitbook.vercel.app/url/gitbook.com/docs	https://8691b741-gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs
E2E	https://b4c3d85c.gitbook-open.pages.dev/gitbook.gitbook.io/test-gitbook-open	https://gitbook-v2-iyjtw9ekt-gitbook.vercel.app/url/gitbook.gitbook.io/test-gitbook-open	https://8691b741-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)	✅ No changes detected	-	Jun 1, 2025, 7:18 PM
customers-v2 (Inspect)	👍 Changes approved	79 changed	Jun 1, 2025, 7:22 PM
default (Inspect)	✅ No changes detected	-	Jun 1, 2025, 7:22 PM
v2-cloudflare (Inspect)	✅ No changes detected	-	Jun 1, 2025, 7:22 PM
v2-vercel (Inspect)	✅ No changes detected	-	Jun 1, 2025, 7:22 PM

[SamyPesse]

I don't see how this is a solution and why we need to change CSS to fix this problem. Maybe I'm missing something, but from my understanding the only solution is to make sure that the inline link doesn't render as a <a>.
I think the best solution is to have a React context in Link.tsx and if it's a nested link, we instead render a <span> with some onClick to trigger navigation (also stop propagation). These <Link> could also re-render after hydration to actually render a <a>.