The use of unrelated StorageKey values for tax rate configurations in the LandManager  reduces code readability, increases the risk of future maintenance errors, and could potentially lead to conflicts if these keys are needed for their original purposes in future updates. Although not a bug per se, this approach introduces subtle risks to the long-term maintainability and extensibility of the system.
In the LandManager contract, tax rates are configured using seemingly unrelated StorageKey values:
https://github.com/code-423n4/2024-07-munchables/blob/94cf468aaabf526b7a8319f7eba34014ccebe7b9/src/managers/LandManager.sol#L65-L72
However, in the IConfigStorage interface, these StorageKey values are defined for different purposes:
While this approach solves the immediate problem of storing new configuration values without updating the StorageKey enum, it introduces subtle issues:
Consider adding  detailed comments in both LandManager and IConfigStorage contracts explaining the repurposing of these StorageKey values for LandManagers tax rates. Also, implement additional checks or assertions in the configuration retrieval process to ensure these StorageKey values are used correctly in different contexts.
