Cardano Updates

Bumps [github.com/blinklabs-io/gouroboros](https://github.com/blinklabs-io/gouroboros) from 0.140.0 to 0.145.0.
- [Release notes](https://github.com/blinklabs-io/gouroboros/releases)
- [Commits](https://github.com/blinklabs-io/gouroboros/compare/v0.140.0...v0.145.0)

---
updated-dependencies:
- dependency-name: github.com/blinklabs-io/gouroboros
  dependency-version: 0.145.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

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

Bumps the dependencies group with 2 updates: [github.com/gdamore/tcell/v2](https://github.com/gdamore/tcell) and [golang.org/x/term](https://github.com/golang/term).


Updates `github.com/gdamore/tcell/v2` from 2.13.2 to 2.13.4
- [Release notes](https://github.com/gdamore/tcell/releases)
- [Changelog](https://github.com/gdamore/tcell/blob/main/CHANGESv3.md)
- [Commits](https://github.com/gdamore/tcell/compare/v2.13.2...v2.13.4)

Updates `golang.org/x/term` from 0.37.0 to 0.38.0
- [Commits](https://github.com/golang/term/compare/v0.37.0...v0.38.0)

---
updated-dependencies:
- dependency-name: github.com/gdamore/tcell/v2
  dependency-version: 2.13.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: golang.org/x/term
  dependency-version: 0.38.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
...

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

Full read-only wallets with accountPubKeyHex can derive addresses directly,
so they don't need to scan transaction history for address discovery.

build(deps): bump actions/cache from 4 to 5

* client-cardano-database from `0.1.38` to `0.1.39`
* client-cardano-database-v2 from `0.1.15` to `0.1.16`
* client-cardano-stake-distribution from `0.1.14` to `0.1.15`
* client-mithril-stake-distribution from `0.2.12` to `0.2.13`
* mithril-cardano-node-chain from `0.1.10` to `0.1.11`
* mithril-cardano-node-internal-database from `0.1.8` to `0.1.9`
* mithril-aggregator-client from `0.1.6` to `0.1.7`
* mithril-dmq from `0.1.14` to `0.1.15`
* mithril-era from `0.1.6` to `0.1.7`
* mithril-protocol-config from `0.1.3` to `0.1.4`
* mithril-ticker from `0.1.4` to `0.1.5`
* mithril-aggregator from `0.7.95` to `0.7.96`
* mithril-client-cli from `0.12.36` to `0.12.37`
* mithril-client-wasm from `0.9.9` to `0.9.10`
* mithril-client from `0.13.0` to `0.13.1`
* mithril-common from `0.6.35` to `0.6.36`
* mithril-relay from `0.1.54` to `0.1.55`
* mithril-signer from `0.2.280` to `0.2.281`
* mithril-aggregator-fake from `0.4.15` to `0.4.16`
* [js] mithril-client-wasm from `0.9.9` to `0.9.10`

- Remove redundant `.map_err(|err| anyhow!(err))` when used before a
  `with_context` as it does the error conversion.
- Remove redundant `format!` in `anyhow!(format!(..))` as the anyhow
  macro already support formatting.
- Prefer usage of `with_context` instead of `ok_or(anyhow!(..))` or
  `ok_or_else(|| anyhow!(..))` when working with options, so the
  error conversion is gracefully done by the anyhow crate instead of
  our code, and this often results in leaner code.
- Simplify `anyhow::anyhow!(e).context(..)` to `e.context(..)` when
  the error is already an anyhow error.
- When using the macro is unavoidable and it print the error in its
  message, add another context layer by wrapping the error first then
  adding the previous message as context.
  e.g: from `anyhow!("Error context: {e}")` to
  `anyhow!(e.to_string()).context("Error context")`.
- Add a anyhow context to some errors.

Note: Some macro usage are unavoidable, e.g when the inner error can't
be implicitly converted to `anyhow::Error`.

Signed-off-by: jeluard <[email protected]>