🐛 Bug: Improve Bowtie Compliance Fetch UX (Loading State, Error Handling, Retry Support)

Describe the bug

The ToolingTable component fetches Bowtie compliance data from:
https://bowtie.report/api/v1/json-schema-org/implementations

Currently, when the request is slow or fails:

• Users receive no clear loading feedback
• Errors are not surfaced in the UI
• There is no retry mechanism
• Accessibility feedback for async updates is limited

This can create confusion when the Bowtie API is temporarily unavailable or slow.

Steps To Reproduce

1. Open the JSON Schema website.
2. Navigate to the Tooling page.
3. Open DevTools → Network tab.
4. Simulate a slow network (e.g., "Slow 3G") OR block the request to:
   https://bowtie.report/api/v1/json-schema-org/implementations
5. Refresh the page.

Current Behavior:

• No visible loading indicator while Bowtie data is being fetched.
• If the request fails (e.g., 404 / network error), the UI does not clearly indicate the failure.
• Users cannot retry fetching Bowtie data without reloading the entire page.
• The Bowtie column may appear empty without explanation.

Expected Behavior

• A loading indicator should appear while fetching Bowtie compliance data.
• If the fetch fails, a visible error message should be shown.
• A retry button should allow re-fetching without reloading the page.
• The UI should provide accessible feedback for screen readers.

Screenshots

No response

Device Information [optional]

- OS:
- Browser:
- version:

Are you working on this issue?

Yes

Do you think this work might require an [Architectural Decision Record (ADR)]? (significant or noteworthy)

No

Start at the ToolingTable component and trace its request to https://bowtie.report/api/v1/json-schema-org/implementations. Check the slow, failed, and successful fetch states, then verify that loading and error feedback are visible, retry works without a page reload, and asynchronous updates are announced accessibly.