fix(filters): keep facet options that appear after a filter change

[grzelaka-roche]

BUG - If guppy/explorer starts with some initial filters and then we drop those filters - the values that didn't exist before in other facets never get displayed.

To reproduce:

• start data-portal with enabled explorerStoreFilterInURL option and some filter in the URL.
• drop that facet filter in the UI
• other facets do not update beyond what was loaded upfront with filter applied

updateCountsInInitialTabsOptions built its output by walking only the frozen initialTabsOptions baseline. When the explorer mounts with a default filter applied, that baseline is captured from an already-filtered aggregation, so bucket keys that surface after an interactive filter change (present in the current response but absent from the baseline) were silently dropped from the UI and could not be displayed or selected.

Build the option universe as the union of the current (processed) response and the frozen baseline: emit all current options first, then re-add baseline-only keys at count 0 to preserve the option-stability feature. The range-filter branch and selectedValues re-add block are unchanged.

Note: this is a partial fix — a companion PR in gen3-ui-component is also required.

This bug has two independent causes in two packages, and both must be fixed for
the facets to display correctly end-to-end:

1. guppy (this PR): updateCountsInInitialTabsOptions dropped bucket keys
   that were absent from the frozen baseline. Fixed here.
2. gen3-ui-component: FilterSection seeds its optionsVisibleStatus
   visibility map only in the constructor and has no getDerivedStateFromProps/
   componentDidUpdate. When props.options grows after an interactive filter
   change (without a remount), options missing from that map are filtered out at
   render time — so even with this guppy fix delivering the full histogram, the
   UI still re-caps the list at the initially-loaded count.

With only this guppy PR, the correct/full option set now reaches the render
layer (verified via logging: the full histogram is passed to the filter
component), but gen3-ui-component then re-drops the newly-arrived options at
render time. The companion fix adds a getDerivedStateFromProps to
FilterSection so options arriving via props after mount become visible while
preserving search-box narrowing.

Companion PR: uc-cdis/gen3-ui-component#248

Link to JIRA ticket if there is one:

New Features

Breaking Changes

Bug Fixes

• Fix explorer facets dropping values that appear only after an interactive filter change. updateCountsInInitialTabsOptions now builds the option list as the union of the current aggregation response and the frozen baseline, instead of restricting output to baseline keys. Note: full end-to-end display also requires the companion gen3-ui-component fix

Improvements

Dependency updates

Deployment changes

[jbarno]

pushed update branch to test out image build push changes are happy.

[grzelaka-roche]

I added gen3-ui-component fix too
uc-cdis/gen3-ui-component#248

This is now ready.