rm bugged force flag from initial mutation test run

Author: bohendo

docs/src/tools/Mutator.md

@@ -12,6 +12,8 @@ You can provide flags to `forge` as part of the `--test-cmd` parameter or target
 
 `slither-mutate src/core/MyContract.sol --test-cmd='forge test --match-contract="MyContract"'`
 
+If a `timout` flag is not provided, slither-mutate will default to using a value that's double the runtime of it's initial test cmd execution. Make sure you run `forge clean` or similar beforehand to ensure cache usage doesn't cause a timeout that's too short to be used; this could lead to false-negatives.
+
 ### CLI Interface
 
 ```shell
@@ -30,7 +32,7 @@ options:
   --test-dir TEST_DIR   Tests directory
   --ignore-dirs IGNORE_DIRS
                         Directories to ignore
-  --timeout TIMEOUT     Set timeout for test command (by default 30 seconds)
+  --timeout TIMEOUT     Set timeout for test command (by default 2x the initial test runtime)
   --output-dir OUTPUT_DIR
                         Name of output directory (by default 'mutation_campaign')
   -v, --verbose         log mutants that are caught, uncaught, and fail to compile

slither/tools/mutator/utils/testing_generated_mutant.py

@@ -40,10 +40,6 @@ def run_test_cmd(
     elif "hardhat test" in cmd or "truffle test" in cmd and "--bail" not in cmd:
         cmd += " --bail"
 
-    if timeout is None and "hardhat" not in cmd:  # hardhat doesn't support --force flag on tests
-        # if no timeout, ensure all contracts are recompiled w/out using any cache
-        cmd += " --force"
-
     try:
         result = subprocess.run(
             cmd,