Adapt API between the platform-sdk and hedera.app for system transaction rafactoring

[mustafauzunn]

In order to support the new format of GossipEvent where transactions will be passed as repeated bytes, we need to extract the parsing of those bytes outside of the platform, so that we have a single common place for this logic. Platform has the need to keep only system transactions, which are handled there.

Good place for this logic will be inside hedera.app, where the transaction bytes will be deserialized back to proto PBJ models, which are the ones utilized by hedera.app logic. Once these PBJ models are created, hedera.app should filter all system transactions and get them back to the platform.

The current design to achieve these requirements is the following:

1. SwirldState.preHandle and SwirldState.handleConsensusRound will be extended with a second argument, which will be a Consumer<ScopedSystemTransaction<StateSignatureTransaction>> callback
2. Inside hedera.app when deserializing of transaction bytes occurs (which will be inside a multi-threaded context), whenever the app sees a StateSignatureTransaction , it will be added in the callback consumer
3. Inside platform-sdk, define these consumer callbacks as input wires inside the wiring framework. This will guarantee transactions coming back from hedera.app are read in a synchronized manner.
4. Handle the incoming system transactions as they are currently processed.

Tasks

Preview Give feedback

1. Enhance SwirldState API with additional callback #16703
   Hedera App Platform +2
   
2. Deserialize transaction bytes and populate callback consumers from SwirldState API #16705
   Hedera App Platform +2
   
3. Consume system transactions from callbacks as inputWires in PlatformWiring #16707
   Platform +1
   
4. Add serialization method for StateSignatureTransaction in hedera.app #17073
   Hedera App Platform +2