docs: Refactor `NotENSv2ReadyBadge` component to remove `"(..)why-ensnode/keep-ens-working"` from `starlightLlmsTxt` excluded list

[Y3drk]

Problem

I had to temporarily exclude the docs/integrate/why-ensnode/keep-ens-working page from the starlightLlmsTxt plugin, because it was causing a build error due to it having a React-based tooltip.

@sevenzing faced the same issue when implementing the OmnigraphStaticExampleSet component.

Why the fix was delayed

• Astro (or Starlight) doesn't currently provide a native, built-in interactive tooltip component
  • I tried to implement one quickly, but it had a bunch of UX holes, and its quality wasn't satisfactory, so I dropped that idea
  • The designs are heavily dependent on the tooltip usage, and I didn't want to break them
• As far as I know, the starlightLlmsTxt plugin is not currently essential for us

Initial fix idea

• I want to try to implement a legitimate Astro-based generic tooltip once we have more time.

[coderabbitai]

🔗 Related PRs

#2201 - chore(docs): Next tranche of ensnode.io UI/UX refinements [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!