Fail on bad scalar conversions

[DavidM-D]

Previously we'd allow bad scalars to be converted too and from bytes. This should be impossible since all conversions are done internally, but it's good to check.

Closes #702

[DavidM-D]

Is it OK that this panics, or should I get it to return a Result?

[volovyks]

We were using the unsafe code to process data provided by the user. As a result, there were no guarantees about the integrity of the data usually provided for an unsafe block of code.

Now we are changing that to a panic() but it is still user-provided data that can crash the program. I would add error handling here, but I see your point, it requires a lot of refactoring.
cc @ChaoticTempest take a look, please.

[DavidM-D]

I'll make it an option, it's actually showing some interesting parts of our codebase. Like what happens if, when deriving epsilon, the output of the hash function doesn't fall into the field?

[ChaoticTempest]

It's fine for now to panic until we get error handling into the contract. At least with this while deriving epsilon, it panics at the entrypoint in the contract before making it to the MPC network. It's kinda buried where this guard is happening but we will have to surface it in a later error handing PR

[github-actions]

Terraform Feature Environment Destroy (dev-703)

Terraform Initialization ⚙️success

Terraform Destroy success

Show Destroy Plan

No changes. No objects need to be destroyed.

Either you have not created any objects yet or the existing objects were
already deleted outside of Terraform.

Destroy complete! Resources: 0 destroyed.

Pusher: @ChaoticTempest, Action: pull_request, Working Directory: ``, Workflow: Terraform Feature Env (Destroy)