Add file id and init bytecode in ContractCallContext

[bilyana-gospodinova]

Description:
During the implementation of the reusable services integration it turns out that now the contracts are deployed in 2 steps:

1. The initcode is uploaded and saved as a file using a FileCreateTransactionBody.
2. The returned file id from step 1 is then passed to a ContractCreateTransactionBody.
   Each step performs a separate transaction.
   For step 2 even if we pass the correct file id, since the mirror node data is readonly, the FileReadableKVState is not able to populate the contract's bytecode from the DB since it was never explicitly persisted in the DB.

This PR add 2 new fields in the ContractCallContext that preserve the file id and the contract's bytecode. If they are available when we call FileReadableKVState#readFromDataSource then we return them with priority.

These two fields might need to be cleared up at some point but this will probably added later when the correct place is found during testing.

Fixes #9798