Upgrade field lib to Plonky3

[hero78119]

With upgrade to plonky3 in unblock many benefits & optimisation possible.

• we can remove in-house version of RowMajorMatrix and just import from plonky3 RowMajorMatrix, and
  • get the basefold encoding via highly optimised FFT library.
  • commit RowMajorMatrix to merkle tree via commit
• remove poseidon porting (code duplicated from plonky2) and use plonky3 poseidon(2)
• Plonky3 support extension field pack/unpack + SIMD via AVX2 or AVX512

TODOs

• upgrade field to plonky3 and ejected from less maintained ceno-Goldilocks
• use RowMajorMatrix to optimize MPCS commitment
• explore SMID optimisation on tower witness inferring/sumcheck
• upgrade to poseidon2
  - see comment Upgrade field lib to Plonky3 #806 (comment)

[hero78119]

Some performance degrade after migrate Poseidon to plonky3 via command cargo bench --bench hashing --package poseidon -- --baseline baseline

Found 2 outliers among 100 measurements (2.00%)
  1 (1.00%) low mild
  1 (1.00%) high mild

ceno hash single        time:   [829.54 ps 830.45 ps 831.39 ps]
                        change: [-0.0836% +0.1065% +0.2809%] (p = 0.25 > 0.05)
                        No change in performance detected.
Found 5 outliers among 100 measurements (5.00%)
  2 (2.00%) high mild
  3 (3.00%) high severe

ceno hash 2 to 1        time:   [2.3006 ms 2.3010 ms 2.3014 ms]
                        change: [+41.410% +41.462% +41.509%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 7 outliers among 100 measurements (7.00%)
  4 (4.00%) high mild
  3 (3.00%) high severe

ceno hash 60 to 1       time:   [19.301 ms 19.306 ms 19.313 ms]
                        change: [+47.062% +47.137% +47.208%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 3 outliers among 100 measurements (3.00%)
  1 (1.00%) high mild
  2 (2.00%) high severe

I think it might be expected due to plonky3 already migrate to poseidon2. We should have sub-task to upgrade poseidon2