feat: Track more information about a note's status and consumability

[tomyrd]

closes #328

This PR looks to add more information about a note status and consumability in the client. This is achieved by a few new features:

• A new NoteStatus variant called Processing was created to represent the state between Comitted and Consumed. It's a state where locally you executed a transaction to consume a note but the client doesn't know if the node confirmed it.
• More metadata about a note's specific status was added inside the different NoteStatus variants:
  • For Pending: A timestamp of the creation of the note in the client.
  • For Commited: The block height where the note was commited in the node.
  • For Processing: The id of the consumer account of the note and the timestamp of the submition of transaction that is currently consuming the note.
  • For Consumed: The id of the consumer account of the note (if known) and the block height where the note was consumed.
• In terms of consumability status, this PR adds a new function (get_note_consumability) to allow the user to check a note's consumability (in addition to the previous get_consumable_notes).

Screenshot of the new status info:

[tomyrd]

Just finished implementing the new additional information for the note status. I also modified the PR title and description to better reflect the new changes.

I feel like all of the other changes discussed here should be implemented in separate PRs. These are the changes that are left unfinished:

• Check if the local consumer transaction actually consumed the note when the nullifier is received. The issue #370 needs to be implemented first.
• Allow for multiple transactions to try to consume the same note locally. We should store each tx trying to consume a note and when it gets nullified we check which tx was commited. This depends on the previous point.
• Find a way to check if a transaction gets cancelled in the node and update the client.