add documentation for reverting txs & gas_limit assignment

Author: zeroXbrock

README.md

@@ -257,7 +257,7 @@ The key directives are:
 
   - `[spam.tx]` defines a single transaction
 
-  - Each tx directive can include various fields such as `to`, `from`, `signature`, `args`, and `value` to specify the details of the transactions or contract interactions.
+  - Each tx directive can include various fields such as `to`, `from`, `signature`, `args`, `value`, and `gas_limit` to specify the details of the transactions or contract interactions.
 
   - `[[spam.bundle.tx.fuzz]]` or `[[spam.tx.fuzz]]`: Configures fuzzing parameters for specific fields in spam transactions, allowing for randomized inputs or ETH values within defined ranges.
 

docs/creating_scenarios.md

@@ -189,6 +189,21 @@ args = ["1350000"]
 
 > 💡 You may want to define different `from_pool` definitions for different kinds of transactions to logically group your agents, which will make your orderflow easier to reason about.
 
+### optional gas limit & sending reverting txs
+
+You have the option to set `gas_limit` to skip gas estimation. This also enables reverting transactions to be sent.
+
+```toml
+[[spam]]
+
+[spam.tx]
+to = "{SpamMe2}"
+from_pool = "bluepool"
+signature = "consumeGas(uint256 gasAmount)"
+args = ["1350000"]
+gas_limit = 1350000
+```
+
 ### sending bundles
 
 The `[spam.tx]` directive sends a mempool transaction using `eth_sendRawTransaction`, but Contender also supports bundles.