[VEN-2100]: Feat timestamp based contracts

[Debugger022]

Description

Resolves #VEN-2100
This PR contains contracts based on Timestamp changes

Checklist

• I have updated the documentation to account for the changes in the code.
• If I added new functionality, I added tests covering it.
• If I fixed a bug, I added a test preventing this bug from silently reappearing again.
• My contribution follows Venus contribution guidelines.

[kkirka]

Thank you for this effort, it was probably quite tedious. I marked some comments with emojis so that you don't spend too much time resolving my "would be nice to have it this way" things 😅

[🤔] – some ideas and thoughts we could discuss, definitely not a blocker for the PR in any way
[🤓] – nerdy nitpicks you might want to address or ignore

[web3rover]

I think we should move the TimeManager contract to https://github.com/VenusProtocol/solidity-utilities. I will be needing the contract for Prime also and we shouldn't import isolated-pools in venus-protocol repo.

Also I think we will need different solidity versions of the contract if we are deploying some of the venus-protocol repo contracts in other chains. For example: XVSVault.

[kkirka]

I think we should move the TimeManager contract to https://github.com/VenusProtocol/solidity-utilities. I will be needing the contract for Prime also and we shouldn't import isolated-pools in venus-protocol repo.

Also I think we will need different solidity versions of the contract if we are deploying some of the venus-protocol repo contracts in other chains. For example: XVSVault.

Maybe the time has come for vault v0.8?

[web3rover]

I think we should move the TimeManager contract to https://github.com/VenusProtocol/solidity-utilities. I will be needing the contract for Prime also and we shouldn't import isolated-pools in venus-protocol repo.
Also I think we will need different solidity versions of the contract if we are deploying some of the venus-protocol repo contracts in other chains. For example: XVSVault.

Maybe the time has come for vault v0.8?

As per my opinion, having a new v0.8 Vault will increase the new feature implementation overheads. I don't see any benefits of having two versions. Even if we create a new version of XVSVault we might still need old version of TimeManager because many other contracts may also need the older version.

If there is any other major benefits of having a v0.8 XVSVault then I would vote for it.

[github-actions]

Package	Line Rate	Branch Rate	Health
contracts	96%	79%	✔
contracts.Gateway	98%	68%	✔
contracts.Gateway.Interfaces	100%	100%	✔
contracts.Lens	95%	73%	✔
contracts.Pool	100%	92%	✔
contracts.Rewards	96%	70%	✔
contracts.RiskFund	89%	61%	✔
contracts.Shortfall	100%	85%	✔
contracts.lib	100%	89%	✔
Summary	96% (1616 / 1682)	76% (540 / 714)	✔