[Feature] Add Field, Group, Scalar, Plaintext, Ciphertext, Transitions, and Transactions to JS SDK.

[iamalwaysuncomfortable]

Motivation

Several feature requests have requested that the ability to the following be added to the SDK.

• Be able to do Field, Group, and Scalar arithmetic and be generally able to work with those types
• Easily peer into Transaction and Transition data and associated inputs and outputs
• Work with Ciphertexts and get items from Struct and Array types

This PR adds these types to the SDK with the ability to turn them into JavaScript/TypeScript objects for convenient extraction of data into a front or backend app as well as api methods that allow these new types to be directly instantiated when calling api endpoints.

It also provides several new typescript types that allow typescript users to work with the JS representation of these objects.

Once this PR is approved, it will constitute the release candidate for the next major version bump.

Test Plan

This PR adds the following unit tests for the new objects:

• Field, Scalar, and Group arithmetic.
• Conversion of Transitions and Transactions to JS objects.

Related PRs

#944 - this PR adds the exports of SnarkVM types to wasm and provides code that

[Pauan]

Some minor nits, but generally looks good.

[Pauan]

Since the docs are being auto-generated by the build:sdk-docs script, shouldn't the .html files be added into .gitignore?

[Pauan]

LGTM

[iamalwaysuncomfortable]

Since the docs are being auto-generated by the build:sdk-docs script, shouldn't the .html files be added into .gitignore?

In theory yes, but in practice when users, especially ones new to the protocol or who aren't great at JS arrive here they don't think to run that. I've found users reaching for the HTML docs immediately and getting use out of it, so this is why it's done currently. We should however replace this with a very prominent link to these documents online. That doesn't exist yet, but I'll talk to @jaketarnow to see if we can make it so.