Retrieve signed data after on chain data has been read

[bdrhn9]

In current implementation, signed data to update beacon is being read early. There are bunch of process after reading signed data until checking conditions to update e.g. initializing Api3ServerV1 contract, initializing sponsor wallet, getting transaction count, initializing void signer, doing some encoding stuff, reading on chain data (multicall). As one can see, only two RPC calls can lead to 30 secs delay because timeout for an RPC call is 15_000 ms. I think more proper approach will be reading signed data from state after on chain data has been fetched.