Rename TDRADE_SATS_PER_BYTE to TX_SATS_PER_BYTE & Fixes

[altafan]

This updates the name of the config env var TDRADE_SATS_PER_BYTE to a more general TX_SATS_PER_BYTE.

The daemon then uses this value for all the transactions it crafts including the trades (as already done originally), and also the fragmentation txs, ie. those txs created by the fee/market fragmenter that split the funds in more fragments before being deposited to the related fee/market account.

Before this, we were hardcoding the 0.1 sats/byte ratio, while now it is configurable through env var.

This also includes fixes to the integration test and docker-compose yaml file.

Please @sekulicd review this.

[what-the-diff[bot]]

PR Summary

• Renaming and Default Value Change in config.go file The TradeSatsPerByte variable has been renamed to TxSatsPerByteKey and its default value adjusted from 0.1 to 0.11. These changes are important for ensuring clarity and consistency in variable naming and values across the codebase.
• Parameter Addition in the NewOperatorService function and NewService function The NewOperatorService and NewService functions have been updated to take an additional satsPerByte parameter. This update lets users input specific transaction speed they want, therefore providing a more flexible service.
• Replacing Hard-Coded Values in the FeeFragmenterSplitFunds and MarketFragmenterSplitFunds functions The hard-coded transaction speed value of 100 in both functions is replaced with the s.milliSatsPerByte value, allowing for greater flexibility in determining transaction speed.
• Change in docker-compose.yml file The wallet service is no longer dependent on the oceand-db container, which helps in improving the modularity and independence of the services.
• Enhancements in the main.go file A variety of changes have been made to improve the functionality of the main function. These changes include the addition of delays to give appropriate time for actions to complete, switching to a pluggable market strategy to allow for different market types, and setting up a market feeder sourcing data from the Kraken source for the XBT/USDT ticker. These changes ensure better functionality and flexibility in the market system.
• Removal of setupTradersWallets function This function was removed as it became unnecessary in the new setup. This leads to cleaner and more efficient codebase.