fix: revert providers outside ErrorBoundary and upgrade findable-ui to v51.1.0

[frano-m]

Summary

Reverts the provider move from #4783 and upgrades findable-ui to v51.1.0, which fixes the infinite crash loop at the library level.

Why revert

PR #4783 moved ExploreStateProvider and DataDictionaryStateProvider inside the ErrorBoundary to catch reducer crashes. This fixed the crash loop but caused state loss when navigating to non-entity-list pages — the providers would unmount and lose explore state.

Why this works without the provider move

findable-ui v51.1.0 (PR #899) fixes the root cause at the library level:

• parseFilterParam — safely validates filter URL params without throwing. Called from reducers above the ErrorBoundary, prevents the crash that caused the re-render loop.
• useValidateFilterParam hook — runs inside ExploreView (inside the ErrorBoundary), validates the URL filter param directly, and throws DataExplorerError for invalid filters so the error page renders.
• ErrorBoundary — fixes this.render → this.reset typo.
• useAsync.run() — clears stale error on new request.

Provider layout (restored to original)

ExploreStateProvider              ← outside ErrorBoundary (preserves state)
  DataDictionaryStateProvider     ← outside ErrorBoundary
    Main
      ErrorBoundary
        FileManifestStateProvider ← inside ErrorBoundary
          Component

Closes #4786

Reference

• Umbrella: Umbrella: roll out filter param validation fix to all findable-ui clients findable-ui#900
• Findable-ui fix: fix: validate filter query params and surface errors inside error boundary (#898) findable-ui#899
• Original bug: Infinite retry loop on 404 when filter query param contains invalid value #4776
• Provider move being reverted: fix: move providers inside ErrorBoundary to prevent crash loop #4783

Test plan

• Malformed JSON filter → error page, no loop
• Wrong shape filter → error page, no loop
• Valid shape, invalid values → API error page, no loop
• Valid filters work normally
• Navigation between entity list and detail pages preserves state
• Unit tests pass
• e2e tests pass

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR reverts the placement of ExploreStateProvider and DataDictionaryStateProvider to be outside the ErrorBoundary (to preserve state across navigation) and upgrades @databiosphere/findable-ui to v51.1.0, which includes upstream fixes to prevent the invalid-filter crash loop without requiring the provider move.

Changes:

• Move ExploreStateProvider and DataDictionaryStateProvider back outside the ErrorBoundary in pages/_app.tsx.
• Upgrade @databiosphere/findable-ui from ^51.0.0 to ^51.1.0 and update lockfile accordingly.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File	Description
pages/_app.tsx	Restores provider layout so explore/data-dictionary state persists even when the error boundary renders.
package.json	Bumps @databiosphere/findable-ui dependency to ^51.1.0.
package-lock.json	Locks @databiosphere/findable-ui to 51.1.0 with updated tarball metadata.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.