chore: g & g_lagrange assignment for ParamsKZG

[luxebeng]

g and g_lagrange is swapped for correctness.

[CPerezz]

Oh wow! This was indeed swapped.

Nice catch!

[CPerezz]

@luxebeng can you fix the actual cloning errors?? I didn't notice that the order swapping would cause those.

[luxebeng]

It's fixed. sorry for the inconvenience.
@CPerezz, would you please grant permission once again?

[jonathanpwang]

Wait, this ordering does not affect correctness: the struct definition does not care about order since the fields are named.
The ordering was done probably to avoid the g.clone()?

[luxebeng]

Wait, this ordering does not affect correctness: the struct definition does not care about order since the fields are named. The ordering was done probably to avoid the g.clone()?

Thank you so much for clarification! this PR will be closed directly.

[CPerezz]

Wait, this ordering does not affect correctness: the struct definition does not care about order since the fields are named.

OMG... I really need to focus more.. Apologies for the inconvenience and thanks for the catch @jonathanpwang