chore: update verification keys

[vplasencia]

Description

This PR adds the new verification keys after the staging ceremony.

This PR should be merged after this: privacy-scaling-explorations/snark-artifacts#80

Aditional info

These are the steps to follow after the real trusted setup ceremony is finished:

1. Clone this repo: https://github.com/vplasencia/semaphorev4-generate-zk-artifacts and run yarn to install dependencies.

2. Add the zkey files to a folder called p0tion-artifacts.

3. Run yarn export-keys.

This will generate two files:

• A file called verification-keys.json with the verification keys for the Semaphore proof package.

• A file called contract-verification-keys.json with the VK_POINTS values for the Semaphore verifier contract.

4. Update the Semaphore repo.

• Update this file with the new values in the verification-keys.json file in the semaphorev4-generate-zk-artifacts project.

https://github.com/semaphore-protocol/semaphore/blob/main/packages/proof/src/verification-keys.json

• Update contract variable with the new values in the contract-verification-keys.json file in the semaphorev4-generate-zk-artifacts project :

semaphore/packages/contracts/contracts/base/SemaphoreVerifier.sol

Line 29 in 5d513f9

uint256[14][MAX_DEPTH] VK_POINTS = [

5. Release a new Semaphore version.

Checklist

• My code follows the style guidelines of this project
• 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
• My changes generate no new warnings
• I have run yarn format and yarn lint without getting any errors
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules