chore(compiler): Update security curves

[BourgerieQuentin]

security estimated using the MATZOV cost model in the lattice estimator
commit: 60808bdc17f99b78bd1bbcd621af04bc6f0e98bb
(see "Report on the Security of LWE: Improved Dual Lattice Attack", April 2022)

close zama-ai/concrete-internal#730

[rudy-6-4]

No longer other curves ?
This is going to break the optimizer CI.

[rudy-6-4]

concrete_security_curves::gaussian::security::supported_security_levels;
is not modified ?

[BourgerieQuentin]

it was not updated so I just update the 128 one, as we use only that on compiler. But @bencrts works on updating the code and all curves we need.

[BourgerieQuentin]

concrete_security_curves::gaussian::security::supported_security_levels; should use generated curves

[github-actions]

Benchmark

Benchmark suite	Current: 8a21fe6	Previous: 52736d4	Ratio
v0 PBS table generation	60820150 ns/iter (± 1076036)	60986750 ns/iter (± 3180220)	1.00
v0 PBS simulate dag table generation	40731906 ns/iter (± 447943)	40885868 ns/iter (± 2036630)	1.00
v0 WoP-PBS table generation	49825307 ns/iter (± 525042)	49846938 ns/iter (± 1239929)	1.00

This comment was automatically generated by workflow using github-action-benchmark.

[bencrts]

The new scripts / curves are here:

https://github.com/zama-ai/parameter-curves

(see the README for the workflow). Currently, there isn't a Makefile etc. Let me know how you want me to proceed, I can either:

(1) just add the raw curve files
(2) add curves + scripts

[rudy-6-4]

The new scripts / curves are here:

https://github.com/zama-ai/parameter-curves

(see the README for the workflow). Currently, there isn't a Makefile etc. Let me know how you want me to proceed, I can either:

(1) just add the raw curve files (2) add curves + scripts

I think (1) is ok for concrete now.
But having (2) + Makefile targets for setup and regen_curves would be better in long term.