feat!: update key parsing

[AaronFeickert]

Description

Updates key parsing to differentiate between canonical- and reduction-based use cases. Makes several updates to account for EpochTime changes. Updates genesis data.

Motivation and Context

An update to tari-crypto differentiates secret key parsing between cases that should use canonical byte arrays, and those that use random byte arrays requiring modular wide reduction.

This PR makes corresponding changes to account for this.

It also makes several updates required since the tari_utilities release used here also makes breaking EpochTime changes that can't be cleanly done separately.

How Has This Been Tested?

Existing tests pass. Uses of parsed secret keys have been manually inspected for correctness.

What process can a PR reviewer use to test or verify this change?

Assert that secret keys and scalars instantiated from byte arrays use the appropriate approach: parsing from canonical byte arrays, or modular wide reduction from uniform byte arrays.

Confirm that EpochTime changes reflect the intended logic, especially relating to timestamp and difficulty handling.

BREAKING CHANGE: This modifies how secret keys and scalars are constructed, and is therefore a breaking change.

[github-actions]

Test Results (CI)

1 243 tests   1 243 ✔️  9m 15s ⏱️
     39 suites         0 💤
       1 files           0 ❌

Results for commit 01fc2ba.

♻️ This comment has been updated with latest results.

[github-actions]

Test Results (Integration tests)

  2 files    1 errors  2 suites   3m 30s ⏱️
14 tests 13 ✔️ 0 💤 1 ❌
15 runs  14 ✔️ 0 💤 1 ❌

For more details on these parsing errors and failures, see this check.

Results for commit 01fc2ba.

♻️ This comment has been updated with latest results.

[stringhandler]

happy with this so far

[AaronFeickert]

Special attention should also be paid to the opcode and script stack changes. It was not clear what the intended handling was for providing verification message data to the relevant opcodes, nor how array data should be parsed to scalars for computation of Ristretto points in scripts.

[AaronFeickert]

This PR now encompasses changes required from a tari_utilities PR that removes certain arithmetic operations from EpochTime. Because these changes are included in the same release as the changes to ByteArray, it's not possible to do separate PRs that will pass testing.

Extra care should be taken to review the EpochTime changes in this PR, since they are used in timestamp and difficulty calculations.

[SWvheerden]

Looking good, just 1 nit about an error type

[AaronFeickert]

Marking as draft to make it clear that merging is blocked on dependency updates. Specifically, tari-crypto needs a new release version.

[SWvheerden]

Replacing with PR: #5900 so that it includes the tari_crypto release tag 0.19.0 instead of the github main branch