Fix logs and start block parameters in oracle deployment

[patitonar]

Closes #233

This PR includes:

• Send transfer watcher logs to remote if configured by also applying logger config to /oracle/docker-compose-transfer.yml file
• Update variable names for start blocks parameter
• If ORACLE_HOME_START_BLOCK or ORACLE_FOREIGN_START_BLOCK are set in playbook configuration the parameters won't be recalculated in oracle/scripts/getValidatorStartBlocks.js

@phahulin please confirm that the deployment and the oracle works correctly with this changes

[phahulin]

Playbook worked, I did a few test transfers and they completed, ex.
Eth -> xDai: https://etherscan.io/tx/0xea4ba2cec581914fce38122a2fb8ef0f02c2ad8fa951fcb1f2c8a45b4393201c
xDai -> Eth: https://blockscout.com/poa/xdai/tx/0x1ea4f185aa627b5cc313773397fc387b26637d96bdadbaffdcb9087d5472f248/internal_transactions

However, I wonder why foreign:nonce key was not set in redis

root@redis:/data# redis-cli
127.0.0.1:6379> keys *
1) "erc-native-transfer:lastProcessedBlock"
2) "home:nonce"
3) "erc-native-collected-signatures:lastProcessedBlock"
4) "erc-native-signature-request:lastProcessedBlock"
5) "erc-native-affirmation-request:lastProcessedBlock"

Does it use the same value on both sides of the bridge now? That's because our validator didn't have luck to generate token transfers on mainnet

[akolotov]

In the file deployment-e2e/molecule/oracle/tests/test_oracle.py we have only checks that rsyslog configuration files exist after the deployment. Does it make sense to extend the tests to detect issues similar to that it is being addressed here?

[patitonar]

Yes, I think there's room for improvement in the tests. Let's create a new issue for this.