Adapt only code where other types don't need to be modified as well.

Making this change also result in updating `TransactionsImporter` and
`BlockRangeRootRetriever` traits methods to use a chain point.

Only `mithril-persistence` is adapted to this changes in this commit.

…ockNumber`

Plus add it to the openapi as it was missing.

Before it was using an ImmutableFileNumber for both bounds

As we can't retrieve the immutable file number associated to a block
number if it's not stored in the database (which will be typically the
case of the upper bound).

Ignoring the lower bound given has parameter.

We ignore it since it's a block number and not a immutable file number
and retrieving the later using the former is difficult since there's no
available function to do that in the cardano api.

…onRepository

As it will be needed from now on to compute the lower bound passed to
the BlockScanner.

With this change the lower bound of the scanner is now based on block
number instead of immutable file number.

* Give the LowerBoundFinder needed by the block scanner
* Remove the transaction 'store' build since it's already provided by the
  transaction 'repository' build

…hainPoint

Note: not compiling, we still need to update the
`CardanoTransactionsSnapshot`.

Leaving only one required to compute the immutable block scanner lower
bound.

Instead of `Epoch,ChainPoint`.

This is because we use this value as the upper bound of the blocks to
import and can't known easily the associated block hash and slot number
needed to constitute a ChainPoint (and we only need them for the lower
bound to allow Pallas to known the starting point).

This force to make the same change to the `TransactionImporter`,
`TransactionRetriever`,`BlockScanner` and the
`CardanoTransactionSnapshot`.

When a lower bound was required this is when we use a
`ChainPoint`(instead of a block number as before). To do this we added a
new condition to the `GetCardanoTransactionQuery` that get the
transactions with the highest block number in db (all transaction with a
same block number also share their slot number and block hash).

Co-authored-by: Sébastien Fauvel <[email protected]>
Co-authored-by: Damien Lachaume <[email protected]>

Since the importer doesn't know anymore about immutable file numbers and
the current block scanner role is precisely to fetch them for its
`ImmutableBlockStreamer`.

Co-authored-by: Sébastien Fauvel <[email protected]>
Co-authored-by: Damien Lachaume <[email protected]>

To compute the block number to be signed based on the chain tip.

Co-authored-by: Sébastien Fauvel <[email protected]>
Co-authored-by: Damien Lachaume <[email protected]>

And pass them where needed to deduce a signed entity type from a time
point.

Also define a default configuration with:
* `security_parameter`: 3000
* `step`: 90

End to end use more lax paramters (security param: 20, step: 15) since
it's far faster and the last transactions we see included have a block
number not that high (arround ~450).

…ransaction

Co-authored-by: Sébastien Fauvel <[email protected]>
Co-authored-by: Damien Lachaume <[email protected]>

By running its `import.sh` script on a 'run only' end to end.

Co-authored-by: Sébastien Fauvel <[email protected]>
Co-authored-by: Damien Lachaume <[email protected]>

Co-authored-by: Sébastien Fauvel <[email protected]>
Co-authored-by: Damien Lachaume <[email protected]>

- Aggregator `cardano_transactions_signing_config.step` from 90 to 120.
- Adjusts/fix multiples comments
- Add missing types in `mithril-client` re-exported common types.

Co-authored-by: Sébastien Fauvel <[email protected]>
Co-authored-by: Damien Lachaume <[email protected]>

Add a test that check the `get_transaction_highest_chain_point` of
the `CardanoTransactionRepository` handle correcly the common case of
multiple transaction with the same chain point.

Clarify cardano transactions artificat builder tests.

Co-authored-by: Sébastien Fauvel <[email protected]>
Co-authored-by: Damien Lachaume <[email protected]>

nodes:
* Mithril-aggregator from `0.5.14` to `0.5.15`
* Mithril-client from `0.8.1` to `0.8.2`
* Mithril-client-cli from `0.9.0` to `0.9.1`
* Mithril-client-wasm from `0.3.1` to `0.3.2`
* Mithril-common from `0.4.11` to `0.4.12`
* Mithril-signer from `0.2.139` to `0.2.140`

websites:
* Mithril-explorer from `0.7.0` to `0.7.1`

internal:
* Mithril-persistence from `0.2.1` to `0.2.2`

test-lab
* Mithril-aggregator-fake from `0.3.1` to `0.3.2`
* Mithril-end-to-end from `0.4.13` to `0.4.14`