Nothing is using these at present. The `sm` size is the same as the
`base` size and helps to show that this app's "base" font size is small.

`lg` will be used by some updated components coming from the shared
component library. The updated scale allows an interim size between
the app's (small) base font and `text-lg`.

Nothing was using the previous `xl` size.

Add `xs` as a new text size equal to the existing `sm` text size and
update components using `text-sm` to use `text-xs`.

This will allow us to change the `sm` size to be the same as the `base`
size.

Update all cases using `text-lg` to use `text-md` (a new text size).
This allows a text size between `base` and `lg`.

There are a few places in the app where we want to size things to 10px,
typically for teeny-tiny icons, but also in one case, some `<sup>` text.

This isn't really a text size, in terms of the relative text-size scale.
Remove the token from the Tailwind config and use a direct pixel size in
the one remaining usage.

In some cases icons are sized relative to local text or containers
(em-based sizing) and that's fine, but using a named text-size
utility directly on an icon can add a layer of unhelpful abstraction if
our intent is simply to size the icon to particular pixel dimensions. It
also entangles icon sizing with text sizing in an unintended way.

In cases where we want to size icons to specific dimensions,
irrespective of local text size, use size utility classes, not text-size
utility classes.

In cases where icons use em-based sizing (e.g. we want to set a text
size on a container such that descendant icons, which are sized at 1em,
have desired dimensions), use arbitrary text sizing classes (e.g.
`text-[16px]` instead of `text-lg`) to be explicit about the intent.

Refactor to relieve a long-standing FIXME in the
`AnnotationShareControl` component, which pre-dates the completion of
the conversion of the app's UI to preact and the full complement of
available store modules.

As groups and annotations are loaded separately, we cannot guarantee
that group metadata is loaded for a given annotation's group (ID).

Attempt to retrieve the annotation's group from the store, and if it
is undefined, don't render the component.

See https://github.com/hypothesis/client/issues/1542

Bumps [setuptools](https://github.com/pypa/setuptools) from 63.2.0 to 65.5.1.
- [Release notes](https://github.com/pypa/setuptools/releases)
- [Changelog](https://github.com/pypa/setuptools/blob/main/CHANGES.rst)
- [Commits](https://github.com/pypa/setuptools/compare/v63.2.0...v65.5.1)

---
updated-dependencies:
- dependency-name: setuptools
  dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>

We aren't tox 4 compatible yet and need to pin it. In Sphinx 5 setting
`language = None` is now frowned upon and raises an error, which causes
us to fail. This removes the line which along with the tox change allows
 doc related tasks to work.

Bumps [axe-core](https://github.com/dequelabs/axe-core) from 4.5.2 to 4.6.2.
- [Release notes](https://github.com/dequelabs/axe-core/releases)
- [Changelog](https://github.com/dequelabs/axe-core/blob/develop/CHANGELOG.md)
- [Commits](https://github.com/dequelabs/axe-core/compare/v4.5.2...v4.6.2)

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

The previous link is no longer extant (redirects to the landing page for
the authoring guide). The current implementation supports the documented
navigation and behavior guidelines in that example, except where not
applicable (e.g. there is no way to explicitly open the listbox if it is
empty). These types of allowed exceptions are alluded to on
https://www.w3.org/WAI/ARIA/apg/patterns/combobox/

Assign `combobox` role to `input` instead of container element in
`TagEditor`.  Remove unneeded `aria-owns` attribute.

This obviates the need to disable any axe-core accessibility tests and
makes tests pass for axe-core v4.6.2.