Cardano Updates

- Pass derivationType from wallet.metadata.trezorConfig to getExtendedAccountPublicKey
- Ensures shared wallet key derivation uses correct derivation path

- Add missing RxJS observables to test mocks for activateWallet
- Fix optional chaining for wallet.metadata in addAccount function
- All 23 tests now pass including addAccount for InMemory, Trezor, and Ledger wallets

- Update @cardano-sdk/web-extension to 0.39.32
- Sync related SDK deps via bump script

- Remove NODE_OPTIONS='--openssl-legacy-provider' from scripts
- The flag was a Node 17/OpenSSL-3 stopgap for old toolchains
(e.g., very old webpack builds). Lace is on modern Node
(see .nvmrc) and current build tooling, so it's not required.

- Add derivationType to WalletMetadata interface
- Store derivation type in wallet metadata during hardware wallet creation
- Update addAccount function to accept and use derivation type
- Pass derivation type from wallet metadata when enabling additional accounts
- Ensures consistent key derivation across all accounts in a hardware wallet

Fixes bug where enabling additional accounts would use default derivation type
instead of the derivation type used when the wallet was originally created.

- Add TrezorDerivationTypeSelector component with UI for selecting derivation types
- Support ICARUS, ICARUS_TREZOR, and LEDGER derivation types
- Add derivationType parameter to createHardwareWalletRevamped function
- Update getHwExtendedAccountPublicKey to pass derivationType to Trezor
- Add DerivationType type export from @lace/cardano
- Add translations for derivation type labels and descriptions
- Show selector conditionally for Trezor devices or when connection is undefined
- Pass derivationType through wallet creation flow to generate correct master key

Removes inaccurate reference to staking keys and clarifies read-only usage

- Update @cardano-sdk/web-extension to 0.39.32
- Sync related SDK deps via bump script

Removes inaccurate reference to staking keys and clarifies read-only usage

- Add derivationType to WalletMetadata interface
- Store derivation type in wallet metadata during hardware wallet creation
- Update addAccount function to accept and use derivation type
- Pass derivation type from wallet metadata when enabling additional accounts
- Ensures consistent key derivation across all accounts in a hardware wallet

Fixes bug where enabling additional accounts would use default derivation type
instead of the derivation type used when the wallet was originally created.

- Add TrezorDerivationTypeSelector component with UI for selecting derivation types
- Support ICARUS, ICARUS_TREZOR, and LEDGER derivation types
- Add derivationType parameter to createHardwareWalletRevamped function
- Update getHwExtendedAccountPublicKey to pass derivationType to Trezor
- Add DerivationType type export from @lace/cardano
- Add translations for derivation type labels and descriptions
- Show selector conditionally for Trezor devices or when connection is undefined
- Pass derivationType through wallet creation flow to generate correct master key

- Remove NODE_OPTIONS='--openssl-legacy-provider' from scripts
- The flag was a Node 17/OpenSSL-3 stopgap for old toolchains
(e.g., very old webpack builds). Lace is on modern Node
(see .nvmrc) and current build tooling, so it's not required.

- Update @cardano-sdk/web-extension to 0.39.32
- Sync related SDK deps via bump script

Sentry release tracking pollutes global scope by declaring 'e'
variable, which can cause conflicts with dapp code when used
in the injected script.

We were NOT using sentry in the content scripts, so this has
no functional effect. The reason that this code was injected
is because we were using the same webpack build configuration
for both: Lace app scripts and content scripts. Webpack plugins
extend compiler behavior globally (applies to all entrypoints).

Sentry release tracking pollutes global scope by declaring 'e'
variable, which can cause conflicts with dapp code when used
in the injected script.

We were NOT using sentry in the content scripts, so this has
no functional effect. The reason that this code was injected
is because we were using the same webpack build configuration
for both: Lace app scripts and content scripts. Webpack plugins
extend compiler behavior globally (applies to all entrypoints).

Sentry release tracking pollutes global scope by declaring 'e'
variable, which can cause conflicts with dapp code when used
in the injected script.

We were NOT using sentry in the content scripts, so this has
no functional effect. The reason that this code was injected
is because we were using the same webpack build configuration
for both: Lace app scripts and content scripts. Webpack plugins
extend compiler behavior globally (applies to all entrypoints).

Bumps [andrcuns/allure-publish-action](https://github.com/andrcuns/allure-publish-action) from 2.9.0 to 2.10.0.
- [Release notes](https://github.com/andrcuns/allure-publish-action/releases)
- [Commits](https://github.com/andrcuns/allure-publish-action/compare/v2.9.0...v2.10.0)

---
updated-dependencies:
- dependency-name: andrcuns/allure-publish-action
  dependency-version: 2.10.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

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