Add `validate_record` API to upgraded contexts

This API serves multiple purposes:

We could never make the existing API work and kept discovering bugs associated with it.

Previously, the validation process was separate, detached from actual protocol and validated everything at once. We saw multiple occurrences where reveal was called before sharings were validated.

Previous approach did not integrate smoothly with vectorization

Vectorization makes data processed in chunks. Going between different chunk sizes (one for data, one for validation) has proven to be challenging. The code written for that was hard to read.

Validate record API

The core of this proposal is to put validate_record API on the UpgradedContext that takes a record_id and blocks the execution until this record (and others in the same batch) has been validated. FWIW this is exactly how ZKP validator works now.

This API allows to bring closer together MAC and ZKP validation.

In addition to bringing this API, this change also updates all the uses of MAC validators and contexts to use it.

The pros include:

Validate record now must be called per record basis, making protocols easier to review. One can see that validate call is there and it is right before the reveal.
Reveal can have special power and abort if the record being revealed hasn't been validated yet. Because UpgradedContext now can keep track of things validated, we can add this functionality later.
No chunk conversion required on the protocol side. They can be simply written w/o doing magic conversions
Validation can now be done in batches, transparently to the code calling validate_record and it integrates smoothly with seq_join (no need for special validated_seq_join)

Downsides:

Tracking total records is difficult. We still don't have a good solution to some of our protocols where we need to have different total records per step, created inside UpgradedContext
record_id appears more and more in the API. Traits like ShareKnownValue must be updated to support it.

Codecov Report

Attention: Patch coverage is 94.72141% with 18 lines in your changes missing coverage. Please review.

Project coverage is 92.77%. Comparing base (468e1e3) to head (322e377). Report is 15 commits behind head on main.

Files	Patch %	Lines
ipa-core/src/protocol/context/batcher.rs	86.11%	10 Missing :warning:
ipa-core/src/protocol/context/malicious.rs	93.65%	4 Missing :warning:
ipa-core/src/protocol/context/semi_honest.rs	0.00%	3 Missing :warning:
ipa-core/src/protocol/context/validator.rs	99.05%	1 Missing :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #1218 +/- ## ========================================== + Coverage 92.69% 92.77% +0.08% ========================================== Files 196 198 +2 Lines 30503 30781 +278 ========================================== + Hits 28274 28558 +284 + Misses 2229 2223 -6 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

private-attribution / ipa