Full Multi-query support onchain

[daveroga]

Implement multi-request support similar to existing requests now in Universal Verifier.

• Manage multi-request (MultiRequest) independently and in the same way we are managing Requests in ZKPVerifierBase now (setMultiRequest, getMultiRequest, …). Avoid ZKP and generalize methods in Requests. setRequest, getRequest, submitResponse, …
• Manage Auth in specific data structure and response.
• Define challenge based on the ethereum address in this first version
• Figure out linkID between the Requests and Auth of the same Query.
• Consider that more than one type of auth may be available there for specific multiRequest. And each of the multiRequests should define it’s own set of valid auth along with requests.
• RequestId change from uint64 to uint256.

Link to Tech Spec for changes: https://www.notion.so/privado-id/Multi-query-Tech-Spec-13d4f86a875180e68fc8e3fa5362805e

[coveralls]

Pull Request Test Coverage Report for Build 13133916940

Details

• 562 of 642 (87.54%) changed or added relevant lines in 33 files are covered.
• 5 unchanged lines in 2 files lost coverage.
• Overall coverage increased (+1.1%) to 85.014%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
contracts/lib/ClaimBuilder.sol	13	14	92.86%
contracts/lib/PrimitiveTypeUtils.sol	3	4	75.0%
contracts/lib/groth16-verifiers/Groth16VerifierAuthV2Wrapper.sol	2	3	66.67%
contracts/lib/groth16-verifiers/Groth16VerifierLinkedMultiQuery10Wrapper.sol	5	6	83.33%
contracts/lib/groth16-verifiers/Groth16VerifierMTPWrapper.sol	2	3	66.67%
contracts/lib/groth16-verifiers/Groth16VerifierSigWrapper.sol	2	3	66.67%
contracts/lib/groth16-verifiers/Groth16VerifierV3Wrapper.sol	2	3	66.67%
contracts/lib/IdentityBase.sol	0	2	0.0%
contracts/validators/request/LinkedMultiQueryValidator.sol	58	60	96.67%
contracts/verifiers/ValidatorWhitelist.sol	6	8	75.0%

Files with Coverage Reduction	New Missed Lines	%
contracts/lib/IdentityBase.sol	1	61.11%
contracts/state/State.sol	4	75.13%

Totals
Change from base Build 13098294824:	1.1%
Covered Lines:	1325
Relevant Lines:	1464

---

💛 - Coveralls

[OBrezhniev]

I think it should be 0x00FFFF... if we want to zero out the first byte.

[daveroga]

Only with the first position as 0 that is 4 bits we have 252 bits remaining for the calculation that fits in a field number. But I could do it with 1 byte if you think it's better an we we'll use 248 bits then.