feat(randomness): submit drands asap

[GabrielMartinezRodriguez]

Description

This PR adds a mechanism to the transaction manager to allow submitting transactions without waiting for a new block to arrive. Additionally, this is implemented in the randomness service to submit drands as soon as they arrive. Thanks to this mechanism, we've achieved a 100% success rate in the sequential randomness of the Randomness contract

• Include all relevant context (but no need to repeat the issue's content).
• Draw attention to new, noteworthy & unintuitive elements.

Toggle Checklist

Checklist

Basics

• B1. I have applied the proper label & proper branch name (e.g. norswap/build-system-caching).
• B2. This PR is not so big that it should be split & addresses only one concern.
• B3. The PR targets the lowest branch it can (ideally master).

Reminder: PR review guidelines

Correctness

• C1. Builds and passes tests.
• C2. The code is properly parameterized & compatible with different environments (e.g. local,
  testnet, mainnet, standalone wallet, ...).
• C3. I have manually tested my changes & connected features.

< INDICATE BROWSER, DEMO APP & OTHER ENV DETAILS USED FOR TESTING HERE >

< INDICATE TESTED SCENARIOS (USER INTERFACE INTERACTION, CODE FLOWS) HERE >

• C4. I have performed a thorough self-review of my code after submitting the PR,
  and have updated the code & comments accordingly.

Architecture & Documentation

• D1. I made it easy to reason locally about the code, by (1) using proper abstraction boundaries,
  (2) commenting these boundaries correctly, (3) adding inline comments for context when needed.
• D2. All public-facing APIs & meaningful (non-local) internal APIs are properly documented in code
  comments.
• D3. If appropriate, the general architecture of the code is documented in a code comment or
  in a Markdown document.
• D4. An appropriate Changeset has been generated (and committed) for changes that touch npm published packages (currently packages/core and packages/react), see here for more info.

[cloudflare-workers-and-pages]

Deploying happychain with    Cloudflare Pages

Latest commit:	280a889
Status:	⚡️  Build in progress...

View logs

[GabrielMartinezRodriguez]

• feat(txm): transactions with value #647 : 2 dependent PRs (#661 , #693 )
• Txm transactions support arbitrary calldata #596
• feat(randomness): submit drands asap #590 👈 (View in Graphite)
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[not-reed]

should this await?

[GabrielMartinezRodriguez]

changed

[not-reed]

i have quite conflicted feelings about decorators 😄

[norswap]

Should we call this sendTransactions? Since if A passes something to B, B is collecting from A. But in this case, A is passing transactions to B, so it's A doing the action :)