Main changes in this PR:
- `BackingStore` and `UniquenessChecker` interfaces are now part of the `ledger-lib-uniqueness` library
- The `BackingStore` logic is basically common for C5 and DLT except for how we establish the DB connection.
   That's the reason we have a base abstract class now called `JPABackingStoreBase`.
   Both C5 and DLT will inherit from this. In C5 it's called `JPABackingStoreOsgiImpl` and the entity manager
   is acquired through `DbConnectionManager`.
- Thankfully the core uniqueness checker logic is the same for C5/DLT so only C5 will extend
  `BatchedUniquenessCheckerImpl` with the necessary OSGi things.
- `BatchedUniquenessCheckerImplTest` tests the main UniquenessChecker logic
- `JPABackingStoreOsgiImplIntegrationTests`, `JPABackingStoreEntitiesIntegrationTest` tests BackingStore in C5.
    We will have testcontainers integration tests in DLT.
- `JPABackingStoreOsgiImplBenchmark` still exists and still works.
- `UniquenessCheckerImplDBIntegrationTests` is the integration test for C5, will have testcontainers version in DLT.

Main changes in this PR:
- `BackingStore` and `UniquenessChecker` interfaces are now part of the `ledger-lib-uniqueness` library
- The `BackingStore` logic is basically common for C5 and DLT except for how we establish the DB connection.
   That's the reason we have a base abstract class now called `JPABackingStoreBase`.
   Both C5 and DLT will inherit from this. In C5 it's called `JPABackingStoreOsgiImpl` and the entity manager
   is acquired through `DbConnectionManager`.
- Thankfully the core uniqueness checker logic is the same for C5/DLT so only C5 will extend
  `BatchedUniquenessCheckerImpl` with the necessary OSGi things.
- `BatchedUniquenessCheckerImplTest` tests the main UniquenessChecker logic
- `JPABackingStoreOsgiImplIntegrationTests`, `JPABackingStoreEntitiesIntegrationTest` tests BackingStore in C5.
    We will have testcontainers integration tests in DLT.
- `JPABackingStoreOsgiImplBenchmark` still exists and still works.
- `UniquenessCheckerImplDBIntegrationTests` is the integration test for C5, will have testcontainers version in DLT.

Co-authored-by: nkovacsx <[email protected]>

…6353)

Put ledger flow code into a new library. Uncoupled the new libraries dependencies and transitive dependencies from the avro schema. Pulling out code where needed into new modules (if there isn't a sensible place).

Co-authored-by: Dan Newton <[email protected]>

…merge-release-branch

R3SOL-0 - merge release branch

…6380)

Extract Block structural verification logic to the ledger library

Extract filtered transactions into the ledger library.

---------

Co-authored-by: Jenny Yang <[email protected]>

restructured C5 to share verification and signing services with corda-dlt
---------
Co-authored-by: PranuR3 <[email protected]>
Co-authored-by: Dan Newton <[email protected]>

- added privacySalt member variable to UtxoTransactionBuilderInternal so that it can be set from dlt and use it for transaction in dlt.
- made conditionally use available privacySalt depending on platform (dlt or c5)

---------

Co-authored-by: Will Vigor <[email protected]>