docs: document allowCheatcodes (#642)

* docs: document allowCheatcodes

* Update src/cheatcodes/allow-cheatcodes.md

src/SUMMARY.md

@@ -236,6 +236,7 @@
       - [`makePersistent`](./cheatcodes/make-persistent.md)
       - [`revokePersistent`](./cheatcodes/revoke-persistent.md)
       - [`isPersistent`](./cheatcodes/is-persistent.md)
+      - [`allowCheatcodes`](./cheatcodes/allow-cheatcodes.md)
       - [`transact`](./cheatcodes/transact.md)
     - [External](./cheatcodes/external.md)
       - [`ffi`](./cheatcodes/ffi.md)

src/cheatcodes/allow-cheatcodes.md

@@ -0,0 +1,19 @@
+## `allowCheatcodes`
+
+### Signature
+
+```solidity
+function allowCheatcodes(address) external;
+```
+
+### Description
+
+In forking mode, explicitly grant the given address cheatcode access.
+
+By default, the test contract, and its deployer are allowed to access cheatcodes. In addition to that, cheat code
+access is granted if the contract was deployed by an address that already has cheatcode access.
+This will prevent cheatcode access from accounts already deployed on the forked network.
+
+> ℹ️ **Note**
+>
+> This is only useful for complexer test setup in forking mode.