[Nakamoto] Warn users about txs that are too big

[friedger]

With Nakamoto, we get fast blocks. However, they are only fast until the budget has been used up.

Therefore, it might not make sense to increase tx fees when the tx is too big for the current tenure.

E.g. the tx below was received at 2024-10-18T11:00:31.000Z and confirmed at 2024-10-18T11:15:52.000Z (~15 minutes later because other big txs of the same address were in the mempool before).

https://api.testnet.hiro.so/extended/v1/tx/0xf2505b210fee6be34d842d9ccb32964e2a1910c7a02cbaf329ca616410407a9a

When users choose to increase fees, they should be aware of their options.

Current solution does not provide any additional information about size or competition:

[linear]

LEA-1587 [Nakamoto] Warn users about txs that are too big

[314159265359879]

Thanks Friedger, I think it would be great if we could show how much of a block dimension a specific transaction would use if included. Namely the dimension it is most heavy on.

If the transaction is "read heavy" show the percentage of "read" it would require from a block.
If the transaction is "write heavy" show that percentage instead. We could show all dimensions but that may be overwhelming and unnecessary.

For context, and for designers who look into this later:
Here you can see the block dimensions (often blocks are full because the maximum read count is reached), when it is full in one dimension though the block is considered full:
https://obycode.github.io/stacks-stats/block/

'Average Fee Rate: 21794 uSTX / % of block' is another unit we could display that can help users see how their current fee compares to other bids. We could convert their fee to uSTX/% of blockspace. This would be in line with what we do on Bitcoin.