TransactionComponent.contextTransactionProcessor() is expensive

In `AbstractContractTransactionHandler.getTransactionComponent()`, a new `TransactionComponent` is created on every contract call, which, along with `TransactionComponent.contextTransactionProcessor()`, is a rather expensive operation, thanks to `dagger` (5% of transaction handling in the `SmartContract` benchmark).
Can passing down dynamic parameters (`HandleContext`, etc.) be done more efficiently?

Start with AbstractContractTransactionHandler.getTransactionComponent() and TransactionComponent.contextTransactionProcessor(), then inspect the SmartContract benchmark mentioned in the issue. Determine whether dynamic parameters such as HandleContext can avoid repeated Dagger component creation while preserving transaction behavior; done means a validated design and measurable reduction in the reported overhead.

Written by the indexing model from the issue text.