New Feature: compute the fingerprint of a Plonk verification key for recursive verification

[weijiguo]

Description

This PR added a new feature to compute the fingerprint (MiMc hash) of a Plonk verification key. The fingerprint could be used to identify a unique verification key or circuit during recursive verification.

Fixes # (issue)
None

Type of change

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How has this been tested?

• Added codes to std/recursion/plonk/verifier_test.go to ensure all curves are supported;
• Added file std/recursion/plonk/vkey_fp_test.go to ensure the correctness of the added functionality.

How has this been benchmarked?

We adopted the snark-friendly hash MiMc to minimize the constraints count. However no benchmark suites were added.

Checklist:

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• I did not modify files generated from templates
• golangci-lint does not output errors locally
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[weijiguo]

This PR depends on #1040

[weijiguo]

Converted to draft. Just came to awareness that MiMc might output different data under different underlying fields. Reviewing impacts.

[CLAassistant]

All committers have signed the CLA.