Updating the feeManger on config will cause desync between bank and vaults
When the bank is initialized it caches the current config.feeManager. This is problematic since feeManger can be updated in config. Since it is precached the address in bank will not be updated leading to a desync between contracts the always pull the freshest value for feeManger and bank.\\n```\\n    feeManager = config_.feeManager();\\n```\\n\\nAbove we see that feeManger is cached during initialization.\\n```\\n    withdrawAmount = config.feeManager().doCutVaultWithdrawFee(\\n        address(uToken),\\n        shareAmount\\n    );\\n```\\n\\nThis is in direct conflict with other contracts the always use the freshest value. This is problematic for a few reasons. The desync will lead to inconsistent fees across the ecosystem either charging users too many fees or not enough.
BlueBerryBank should always use config.feeManger instead of caching it.
After update users will experience inconsistent fees across the ecosystem
```\\n    feeManager = config_.feeManager();\\n```\\n