refactor: simplify block limit error messages

[Troublor]

Summary

Improve block limit error messages to accurately reflect the limit checking logic:

• Post-execution limits (data, KV, compute gas, state growth):

  • Remove tx_used field since it's always 0 when the error is thrown
  • Use "reached" with >= to reflect the actual check condition (block_used >= limit)
  • These errors occur when the block already exceeded limits from a previous transaction

• Pre-execution limits (encode size, DA size):

  • Keep tx_used field since the current transaction's size is relevant
  • Use "exceeded" with + and > since these check block_used + tx_used > limit

Test plan

• cargo check passes