Add test config in zero bin

[sai-deng]

#676 Now, with the --use-test-config flag, you should see a significant speed gain when running tests with Zero Bin. In the example below, execution time was reduced by around 48% when proving blocks on the testnet.

Before

 Performance counter stats for './target/release/leader --runtime in-memory -b 10 -m 19 -n 12 rpc --rpc-url http://35.242.167.249:18545 --block-interval 448 --checkpoint-block-number 447':

       21864778.01 msec task-clock                       #   19.499 CPUs utilized          
          13790664      context-switches                 #  630.725 /sec                   
            820894      cpu-migrations                   #   37.544 /sec                   
          17892006      page-faults                      #  818.303 /sec                   
   <not supported>      cycles                                                      
   <not supported>      instructions                                                
   <not supported>      branches                                                    
   <not supported>      branch-misses                                               

    1121.328607001 seconds time elapsed

   21344.317469000 seconds user
     538.293330000 seconds sys

After

Performance counter stats for './target/release/leader --use-test-config --persistence none --runtime in-memory -b 10 -m 19 -n 12 rpc --rpc-url http://35.242.167.249:18545 --block-interval 448 --checkpoint-block-number 447':

       13871088.09 msec task-clock                       #   23.721 CPUs utilized          
           9171155      context-switches                 #  661.171 /sec                   
            497524      cpu-migrations                   #   35.868 /sec                   
          10917169      page-faults                      #  787.045 /sec                   
   <not supported>      cycles                                                      
   <not supported>      instructions                                                
   <not supported>      branches                                                    
   <not supported>      branch-misses                                               

     584.763748797 seconds time elapsed

   13490.322378000 seconds user
     392.407730000 seconds sys

[0xaatif]

Can you explain what unsafe means here? What's the tradeoff to the user? What does it mean if it passes?

[sai-deng]

unsafe may not be the appropriate term here. I've updated the comments to reflect that. Passing tests with use_test_config confirms the logic and correctness of the code, but it doesn't guarantee the security of the proofs generated, as this configuration sacrifices security for speed.

[0xaatif]

I don't really understand what security means in this context, but I'm happy with the change

[sai-deng]

Our current STARK configuration targets a 100-bit security level, meaning an attacker would need to make 2^100 attempts to create a fraudulent proof that the verifier would accept. However, we can lower this security level (allowing an attacker to require significantly fewer attempts to create a fraudulent proof) in exchange for faster performance during testing.

[Nashtare]

@0xaatif are you good with this part, or should Sai reword the one-liner?

[LindaGuiga]

LGTM

[Nashtare]

LGTM, thanks!