This is a little premature, but by the time 1.0 is ready Python 3.8
will be end of life so we may as well drop support for it now

Using `from __future__ import annotations` in more places meant that
the field's types were coming through as strings. Using
`typing.get_type_hints` ensures that these references are resolved
correctly.

Bumps [@vscode/vsce](https://github.com/Microsoft/vsce) from 2.30.0 to 2.31.1.
- [Release notes](https://github.com/Microsoft/vsce/releases)
- [Commits](microsoft/vscode-vsce@v2.30.0...v2.31.1)

---
updated-dependencies:
- dependency-name: "@vscode/vsce"
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

Bumps [semver](https://github.com/npm/node-semver) from 7.6.2 to 7.6.3.
- [Release notes](https://github.com/npm/node-semver/releases)
- [Changelog](https://github.com/npm/node-semver/blob/main/CHANGELOG.md)
- [Commits](npm/node-semver@v7.6.2...v7.6.3)

---
updated-dependencies:
- dependency-name: semver
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

updates:
- [github.com/astral-sh/ruff-pre-commit: v0.5.2 → v0.5.4](astral-sh/ruff-pre-commit@v0.5.2...v0.5.4)
- [github.com/pre-commit/mirrors-mypy: v1.10.1 → v1.11.0](pre-commit/mirrors-mypy@v1.10.1...v1.11.0)

By the time the `1.0` release is ready, Sphinx 8.x will be available,
so it makes sense to try and add support for it now.

Nothing against furo, but not depending on it for test cases is one
less dependency to migrate when a major version of Sphinx rolls
around.

Plus overriding the theme set in `conf.py` is a nice way to exercise
the `configOverrides` option

updates:
- [github.com/astral-sh/ruff-pre-commit: v0.5.4 → v0.5.6](astral-sh/ruff-pre-commit@v0.5.4...v0.5.6)
- [github.com/pre-commit/mirrors-mypy: v1.11.0 → v1.11.1](pre-commit/mirrors-mypy@v1.11.0...v1.11.1)

* build(deps-dev): bump typescript from 5.5.3 to 5.5.4 in /code

Bumps [typescript](https://github.com/Microsoft/TypeScript) from 5.5.3 to 5.5.4.
- [Release notes](https://github.com/Microsoft/TypeScript/releases)
- [Changelog](https://github.com/microsoft/TypeScript/blob/main/azure-pipelines.release.yml)
- [Commits](microsoft/TypeScript@v5.5.3...v5.5.4)

---
updated-dependencies:
- dependency-name: typescript
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Alex Carney <[email protected]>

Bumps [ovsx](https://github.com/eclipse/openvsx/tree/HEAD/cli) from 0.9.1 to 0.9.2.
- [Release notes](https://github.com/eclipse/openvsx/releases)
- [Changelog](https://github.com/eclipse/openvsx/blob/master/cli/CHANGELOG.md)
- [Commits](https://github.com/eclipse/openvsx/commits/HEAD/cli)

---
updated-dependencies:
- dependency-name: ovsx
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

This commit extends the Sphinx Process tree view to include additional
details about the Sphinx processes currently managed by the server.

- The value of `esbonio.sphinx.pythonCommand`
- The value of `esbonio.sphinx.buildCommand`
- The current builder name, as well as a (basic!) file tree exposing the
  contents of the build directory. This finally makes the files produced
  when esbonio writes to its default build dir easily accessible.

Including these details not only helps the user figure out the current
state of the server, but it provides an obvious location for additional
management/maintainance commands in the future

To remove the possibility of conflicting with extensions that introduce
custom doctree nodes, the sphinx agent will only consider nodes defined
in `docutils.nodes` or `sphinx.addnodes` when injecting line numbers

The most recent release of pytest-lsp now surfaces the above issue in
the test suite. So that esbonio is not blocked on a fix, wrap the call
to `shutdown_session` in `asyncio.wait_for` and ignore the timeout error.

Bumps [platformdirs](https://github.com/tox-dev/platformdirs) from 4.2.2 to 4.3.3.
- [Release notes](https://github.com/tox-dev/platformdirs/releases)
- [Changelog](https://github.com/tox-dev/platformdirs/blob/main/CHANGES.rst)
- [Commits](tox-dev/platformdirs@4.2.2...4.3.3)

---
updated-dependencies:
- dependency-name: platformdirs
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

Bumps [websockets](https://github.com/python-websockets/websockets) from 12.0 to 13.0.1.
- [Release notes](https://github.com/python-websockets/websockets/releases)
- [Commits](python-websockets/websockets@12.0...13.0.1)

---
updated-dependencies:
- dependency-name: websockets
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>