Removing private transaction management features

[matthew1001]

PR description

As part of Besu's enterprise roadmap and in support of making Besu more modular and composable, private transaction features are being removed as complimentary projects such as Paladin gain traction as privacy solutions for Besu and other EVMs.

This PR removes the previous private transaction management feature including support for Tessera.

Known TODOs:

• Make Besu tolerant of private transactions in historic blocks, but don't attempt to execute them
  • We have tested this with historic blocks containing PMTs, both with block import and syncing with nodes
  • One thing the PR adds is @JsonIgnoreProperties({"privacyVersion"}) for MetadataV2 so a user with privacyVersion in their database metadata file doesn't need to manually edit it to start the node.

Summary of tests carried out with existing PMT transactions after upgrading to non-privacy version of Besu:

• Upgrade/replace a privacy-enabled validator node with privacy-removed besu on existing chain with PMTs (keep data folder intact)
  • Starts and ignores existing privacyVersion field in DB metadata file
• Upgrade a privacy-disabled validator node with privacy-removed besu on existing chain with PMTs (keep data folder intact)
  • Comes up with no issues and continues to mine
• Add a new privacy-removed non-validator node on existing chain with PMTs
  • Syncs fine

[macfarla]

started 3 mainnet nodes (2 checkpoint and 1 snap) off this branch, and 2 control nodes off latest main, all bonsai

• vm_name: dev-elc-bu-nb-mainnet-rm-privacy-test-1
• vm_name: dev-elc-bu-nb-mainnet-rm-privacy-test-2
• vm_name: dev-elc-bu-nb-mainnet-rm-privacy-test-3
• vm_name: dev-elc-bu-nb-mainnet-rm-privacy-control-1
• vm_name: dev-elc-bu-nb-mainnet-rm-privacy-control-2

[macfarla]

remove privacy branch looks to have similar behaviour to main when it comes to syncing mainnet so think we can say it's safe to make the change.