fix: Adapt STARK verifier to Triton VM prover v0.40

A slight change was made in Triton VM's STARK protocol, as the
base/ext/quotient *and* deep codeword weights are now all sampled
through one sponge operation, whereas this was previous two, one for
base/ext/quotient and another one for the deep codeword weights.

This saves 18(!) in the dominating table height, which is the op-stack
table, so it's not exactly a huge performance boost but admittedly a bit
cleaner way of sampling weights.

tasm-lib/benchmarks/tasmlib_recufier_stark_verify_256.json

@@ -2,11 +2,11 @@
   {
     "name": "tasmlib_recufier_stark_verify_256",
     "benchmark_result": {
-      "clock_cycle_count": 1194016,
+      "clock_cycle_count": 1193994,
       "hash_table_height": 181747,
-      "u32_table_height": 45332,
-      "op_stack_table_height": 1637778,
-      "ram_table_height": 513216
+      "u32_table_height": 45726,
+      "op_stack_table_height": 1637760,
+      "ram_table_height": 513214
     },
     "case": "CommonCase"
   }

tasm-lib/benchmarks/tasmlib_recufier_stark_verify_512.json

@@ -2,11 +2,11 @@
   {
     "name": "tasmlib_recufier_stark_verify_512",
     "benchmark_result": {
-      "clock_cycle_count": 1221679,
+      "clock_cycle_count": 1221657,
       "hash_table_height": 190879,
-      "u32_table_height": 51283,
-      "op_stack_table_height": 1675336,
-      "ram_table_height": 516823
+      "u32_table_height": 51160,
+      "op_stack_table_height": 1675318,
+      "ram_table_height": 516821
     },
     "case": "CommonCase"
   }