The `CloseButton` component in @hypothesis/frontend-shared has styling that
makes it taller (44px) on touch devices, but the `Tab` component does not. Items
in the `TabHeader` are centered on the cross axis, so on mobile, the close
button became taller than the tabs and detached them from the tab panel.

An alternative way to fix this would be to make tabs also grow in height on
touch devices, but they are quite usable without.

Fixes https://github.com/hypothesis/client/issues/6131

Prevent the filter toggle button row from overflowing the containing panel by
wrapping onto multiple lines if needed, and truncate long labels within
individual toggle buttons if needed.

Fixes https://github.com/hypothesis/client/issues/6140

Remove the `search_panel` feature flag tests and old search UI.

This fixes an issue on smaller iOS devices (eg. iPhone) where the browser zooms
in when an input field with < 16px font size is tapped. This change ought to be
applied to the `Input` component in the pattern library, but until then, apply
it to input fields in the client.

This change was taken from the `MarkdownEditor` component.

There was already a solution for this issue implemented in `SearchIconButton`.
Extract that into a component that the other top bar buttons can use.

Part of https://github.com/hypothesis/client/issues/6131.

Adjust icon placement per feedback in
https://github.com/hypothesis/client/pull/6130#pullrequestreview-1838479102.

Align the styling of the search/clear buttons with the mocks [1] by:

 - Making the icons visually part of the input field
 - Increasing their size to match the top bar icons
 - Adjusting the padding

[1] https://github.com/hypothesis/client/issues/6006#issuecomment-1887328191

Move the screen-reader only summary element outside of the container with
spacing between elements, as this caused the tab titles to shift down.

In the new search UI there is no longer a status message which tries to describe
the search result counts in detail. Instead we rely on the existing counts that
are displayed on tab titles.

Add a hidden status message with `role="status", aria-live="polite"` to
communicate changes in these counts to assistive technology users.

Part of https://github.com/hypothesis/client/issues/6006

Bumps the sentry group with 2 updates: [@sentry/browser](https://github.com/getsentry/sentry-javascript) and [@sentry/cli](https://github.com/getsentry/sentry-cli).


Updates `@sentry/browser` from 7.93.0 to 7.94.1
- [Release notes](https://github.com/getsentry/sentry-javascript/releases)
- [Changelog](https://github.com/getsentry/sentry-javascript/blob/develop/CHANGELOG.md)
- [Commits](https://github.com/getsentry/sentry-javascript/compare/7.93.0...7.94.1)

Updates `@sentry/cli` from 2.25.0 to 2.25.3
- [Release notes](https://github.com/getsentry/sentry-cli/releases)
- [Changelog](https://github.com/getsentry/sentry-cli/blob/master/CHANGELOG.md)
- [Commits](https://github.com/getsentry/sentry-cli/compare/2.25.0...2.25.3)

---
updated-dependencies:
- dependency-name: "@sentry/browser"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: sentry
- dependency-name: "@sentry/cli"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: sentry
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps [sass](https://github.com/sass/dart-sass) from 1.69.7 to 1.70.0.
- [Release notes](https://github.com/sass/dart-sass/releases)
- [Changelog](https://github.com/sass/dart-sass/blob/main/CHANGELOG.md)
- [Commits](https://github.com/sass/dart-sass/compare/1.69.7...1.70.0)

---
updated-dependencies:
- dependency-name: sass
  dependency-type: direct:development
  update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps the rollup group with 1 update: [rollup](https://github.com/rollup/rollup).


Updates `rollup` from 4.9.5 to 4.9.6
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](https://github.com/rollup/rollup/compare/v4.9.5...v4.9.6)

---
updated-dependencies:
- dependency-name: rollup
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: rollup
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps [prettier](https://github.com/prettier/prettier) from 3.2.2 to 3.2.4.
- [Release notes](https://github.com/prettier/prettier/releases)
- [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prettier/prettier/compare/3.2.2...3.2.4)

---
updated-dependencies:
- dependency-name: prettier
  dependency-type: direct:development
  update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps the eslint group with 2 updates: [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin) and [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser).


Updates `@typescript-eslint/eslint-plugin` from 6.18.1 to 6.19.0
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v6.19.0/packages/eslint-plugin)

Updates `@typescript-eslint/parser` from 6.18.1 to 6.19.0
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/parser/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v6.19.0/packages/parser)

---
updated-dependencies:
- dependency-name: "@typescript-eslint/eslint-plugin"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: eslint
- dependency-name: "@typescript-eslint/parser"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: eslint
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps [aws-sdk](https://github.com/aws/aws-sdk-js) from 2.1536.0 to 2.1540.0.
- [Release notes](https://github.com/aws/aws-sdk-js/releases)
- [Commits](https://github.com/aws/aws-sdk-js/compare/v2.1536.0...v2.1540.0)

---
updated-dependencies:
- dependency-name: aws-sdk
  dependency-type: direct:development
  update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps [autoprefixer](https://github.com/postcss/autoprefixer) from 10.4.16 to 10.4.17.
- [Release notes](https://github.com/postcss/autoprefixer/releases)
- [Changelog](https://github.com/postcss/autoprefixer/blob/main/CHANGELOG.md)
- [Commits](https://github.com/postcss/autoprefixer/compare/10.4.16...10.4.17)

---
updated-dependencies:
- dependency-name: autoprefixer
  dependency-type: direct:development
  update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>

When a selection exists, it replaces other filters rather than being combined
with them. Disable the other filter controls in the UI in this case to make it
more obvious how the filters are being applied.

Several pieces of code tested only for the presence of keys in `focusFilters` to
determine whether a focus filter was configured, rather than whether the
property was set to a "valid" value for that particular filter. The
`changeFocusModeUser` store action would always set this property, instead of
removing it when the passed user info was empty (logically meaning "no user is
focused").

Fixes https://github.com/hypothesis/client/issues/6109

When the user clicks highlight(s) in the document and makes a "selection" in the
sidebar, we want the selected threads to always be visible. Previously this was
handled by clearing other types of filter when the selection was made, in
addition to setting the selection. This however meant that after the selection
was cleared, the state was different than prior to making the selection, with
any non-selection filters being disabled.

This commit changes the behavior so that the selection, if present, temporarily
overrides other filters rather than being combined with them. This allows the
selection to later be removed to revert back to the previous state.

When focus filters are in use (eg. user / page filters) it is annoying if
clicking a highlight in the document and then clearing the selection has the
effect of disabling the focus filters. Instead the plan is to have the selection
temporarily replace filters when active.

When the search panel is open, filter controls are displayed inside it. To make
filter controls accessible when the search panel is closed, render standalone
controls from `SidebarView`, wrapper in a container card.

Rendering of the card is handled by `FilterControls`, so that the logic for
conditionally rendering depending on whether filters are configured, does not
need to be duplicated.

Now that the icon has been added to @hypothesis/frontend-shared, use it
in the filter controls.

Update style of filter toggle buttons to align them with the current mocks.
Also fix accessibility of the pressed state by using the `pressed` button prop
to indicate whether the toggle is active.

Part of https://github.com/hypothesis/client/issues/6006.

Update the watch glob used by the gulp task.

Take initial steps to update the design of the search panel and filter controls
to align with the mocks in https://github.com/hypothesis/client/issues/6006.

 - Move the filter status UI into the search panel. This reduces the amount of
   vertical space required when a search and/or filter are active.

 - Replace the filter status description string + single filter state toggle
   with a row of toggle buttons, one per filter.

   Using one toggle button per filter allows the user to toggle the different
   filter states independently. Removing the filter description saves space and
   also it was getting increasingly complicated to construct descriptions of all
   the possible search/filter combinations.

As part of the filter UI overhaul we want to make it easier to toggle filters
independently, which enables going back / forward one step at a time. For the
search panel, this means that closing search should not affect other filters.