feat(connector-besu): remove tessera support

[petermetz]

BREAKING CHANGE

Besu has deprecated privacy features and since we are coming up on a major release we should also use this opportunity to reduce complexity in the Besu connector by eliminating the associated features from the connector itself and from the testing infrastructure as well (Besu AIO container image).

Tessera-based privacy is deprecated in Besu version 24.12.0 and later. Please read this blog post for more context on the rationale behind this decision as well as alternative options.

Source 1: https://besu.hyperledger.org/private-networks/concepts/privacy
Source 2: https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu

Implementation Notes

You can search for .priv. in your favorite IDE and filter the results to .ts file extensions which then will give you a (probably/hopefully) comprehensive list of places in the code where privacy features are being used.
These all need to be removed and the corresponding public API surface features removed as well.

cc: @hyperledger-cacti/cacti-maintainers

[outSH]

Since privacy features in besu were main differentiator from geth and other standard ethereum implementations, maybe it'd be better to consolidate this connector with cactus-plugin-ledger-connector-ethereum? Sadly I didn't have any time to work on my connector inheritance idea (that would be great for this scenario), but I think if there are little differences and JSON-API is basically the same I don't think there's a strong need for duplicated code

[petermetz]

@outSH I agree. We could retire one or the other connector as of v3.0.0 (where we can make breaking changes) just have to make sure the features are merged all together so nobody gets left behind in that sense.