BaseTradeExecutor.confirmDeposit | confirmWithdraw - Violation of the “checks-effects-interactions” pattern
Both `confirmDeposit, confirmWithdraw` might be re-entered by the keeper (in case it is a contract), in case the derived contract allows the execution of untrusted code.\\n```\\nfunction confirmDeposit() public override onlyKeeper {\\n    require(depositStatus.inProcess, "DEPOSIT\\_COMPLETED");\\n    \\_confirmDeposit();\\n    depositStatus.inProcess = false;\\n}\\n```\\n\\n```\\nfunction confirmWithdraw() public override onlyKeeper {\\n    require(withdrawalStatus.inProcess, "WIHDRW\\_COMPLETED");\\n    \\_confirmWithdraw();\\n    withdrawalStatus.inProcess = false;\\n}\\n```\\n
Although the impact is very limited, it is recommended to implement the “checks-effects-interactions” in both functions.
```\\nfunction confirmDeposit() public override onlyKeeper {\\n    require(depositStatus.inProcess, "DEPOSIT\\_COMPLETED");\\n    \\_confirmDeposit();\\n    depositStatus.inProcess = false;\\n}\\n```\\n