[AnVIL DX] Upgrade findable-ui with filter param validation fix

[frano-m]

Summary

Upgrade @databiosphere/findable-ui to the version containing the filter param validation fix (findable-ui#899) and revert the provider move from #4783.

What needs to happen

1. Revert ExploreStateProvider and DataDictionaryStateProvider to their original position outside the ErrorBoundary in pages/_app.tsx. Moving them inside (fix: move providers inside ErrorBoundary to prevent crash loop #4783) caused state loss when navigating to non-entity-list pages.

2. Upgrade findable-ui to pick up the filter param validation fix, which handles the crash loop at the library level instead:

   • parseFilterParam safely parses filter URL params without throwing (prevents reducer crash above ErrorBoundary)
   • useValidateFilterParam hook surfaces invalid filter errors inside the ErrorBoundary (renders error page)

Context

The original fix (#4783) moved providers inside the ErrorBoundary to catch reducer crashes. This worked for the crash loop but broke state preservation on navigation. The findable-ui fix (#899) solves the root cause — invalid filter params are validated defensively in the reducer path and errors are surfaced via a hook inside the ErrorBoundary.

Reference

• Umbrella: Umbrella: roll out filter param validation fix to all findable-ui clients findable-ui#900
• Findable-ui fix PR: 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 (to be reverted): fix: move providers inside ErrorBoundary to prevent crash loop #4783