feat: improve logging system in terminal and UI

[denishacquin]

Fixes #448
Fixes #436

What

• Refactored and improved the overall logging system for RPC, GenVM, consensus, both in backend and in frontend.
• Display live transaction status updates in both terminal and frontend logs
• Added filtering capabilities in the UI
• Added ability to filter by tx hash directly from transaction items
• Removed some unused logic in the frontend

Here's the list of events that trigger logs:

const trackedEvents = [
    'endpoint_call',
    'endpoint_success',
    'endpoint_error',
    'transaction_status_updated',
    'consensus_data_updated',
    'read_contract',
    'write_contract',
    'write_contract_failed',
    'deploying_contract',
    'deployed_contract',
    'contract_deployment_failed',
  ];

Why

• To improve debugging and overall developer experience

Testing done

• e2e
• unit
• integration
• error handling for each case

Decisions made

• Added loguru python package for easy colored logs
• Introduced some types for the new events in the backend to enforce type safety
• Decided to keep llm calls and get page for later as the context is different more tricky to implement

Checks

• I have tested this code
• I have reviewed my own PR
• I have created an issue for this PR
• I have set a descriptive PR title compliant with conventional commits

Reviewing tips

• Need special attention on the message handler class
• Check out the terminal and play around with the logs to try the new features
• Not 100% sure we should print the payloads in the terminal, it's a lot of clutter (we were doing it before)

User facing release notes

• Improved logging of key events in the backend terminal
• Improved logging in the UI
• Added filtering capabilities in the logs in the UI

[AgustinRamiroDiaz]

@denishacquin please also fix backend unit tests

[AgustinRamiroDiaz]

What's the reason behind this change?

[denishacquin]

It was redundant because we also update the status in the update status method, and I thought it was causing the unit test to fail. But actually updating the mocking in the test was enough, so I'm reverting this! nevermind

[sonarcloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarCloud

[github-actions]

🎉 This PR is included in version 0.13.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀