[framework] Make use of the Clock for Timelock

[miker83z]

• change the unlock function to support Clock
• consider whether to update the check_expiration_timestamp_ms with Clock
• update tests accordingly

Could be part of Protocol Upgrade 3 with #4592

[alexsporn]

You can target the #4741 feature branch

[miker83z]

To check if changing the unlock function breaks the ledger (testnet and devnet, right now). If not, it is still worth to discuss whether we want to keep a unlock function using the epoch timestamp and an unlock_with_clock, or just keep the second one. @valeriyr @lzpap

[lzpap]

Changing the function signature of a public method should definitely break the backwards compatibility @miker83z

[valeriyr]

@miker83z @lzpap Yes, adding the clock parameter makes the iota-framework framework incompatible with version 1:

---- compatibility_tests::test_framework_compatibility stdout ----
thread 'compatibility_tests::test_framework_compatibility' panicked at crates/iota-framework-snapshot/tests/compatibility_tests.rs:37:21:
The current Iota framework 0x0000000000000000000000000000000000000000000000000000000000000002 is not compatible with version 1

I will add new functions.