[Feat:] Time consensus implementation

[jaoleal]

Since #198 became abandoned and wasnt updated i decided to reimplement what was done from that PR.

This PR tries to add the validation for Time related data to floresta.
To implement this i ran trough some solutions and here they are:

• locktime inside the transactions: To validate them i need the MTP and the timestamp of the block when the utxo was created.
• Block Timestamp: To validate if a block is inserting the correct timestamp i need the MTP of the chain.

This changes implements a new struct and a trait on mod and a new function on Consensus .

• Trait NodeTime was made just to delegate real-time notion of time.
• Struct Utxo_Data for holding the utxo together with block-height and time data of the commitment of the utxo, when it was created.
• validate_locktime method inside Consensus to consume the other solutions (MTP, UTXO TIME-DATA) and to validate time itself.

The work from now on in this PR is:

• Include validate_locktime and populate support for it, changing some methods signature(including validate_transactions, validate_block and etc...).
• Implement a way of having MTP notion. Its a problematic because of how we organize our IBD and i dont have a good solution for it, besides including MTP validation only after the chain is validated(any thoughts on this ?).

[jaoleal]

My master was behind 0.7.0 bump.
@Davidson-Souza you can tag this as 0.8.0 milestone

[Davidson-Souza]

Overall looks good, some implementation comments.

[jaoleal]

Applied changes by @Davidson-Souza.

4cc0df3 Tries to implement get_mtp() to be used after IBD due to the fact that a PartialChainState isnt too reliable to process this data.

Note to reviewers

Im still not glad with this solution to validate time-related data and still a lot of work to do around this changes.

I would like to:

1. Completely delete UtxoMap to stop the conflict between hashmaps.
2. (Possibly) Implement get_mtp() for PartialChainState using blockheaders but i still need to understand its behavior in runtime.
3. Remove the usage of UtxoData too, but this would need to store height and time info on a separate location since its crucial to validate locktime.