fix: add missing fields to execution outcome and test

[austinabell]

Pre-flight checklist

• I have read the Contributing Guidelines on pull requests.
• Commit messages follow the conventional commits spec
• If this is a code change: I have written unit tests.
• If this changes code in a published package: I have run pnpm changeset to create a changeset JSON document appropriate for this change.
• If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

This RPC type is missing fields that are required for proof verification. There is another metadata field and compute_usage fields that are missing also, but I opted to keeping these changes light.

I defaulted to having this be a patch changeset, but can change to minor if intended. Unclear how semver is with TS adding fields to interfaces (esp in this case since those types shouldn't be constructed manually)

Test Plan

updated an existing test

Related issues/PRs

[changeset-bot]

🦋 Changeset detected

Latest commit: 188107a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 14 packages

Name	Type
@near-js/types	Patch
@near-js/accounts	Patch
@near-js/crypto	Patch
@near-js/keystores	Patch
near-api-js	Patch
@near-js/providers	Patch
@near-js/transactions	Patch
@near-js/utils	Patch
@near-js/wallet-account	Patch
@near-js/cookbook	Patch
@near-js/biometric-ed25519	Patch
@near-js/keystores-browser	Patch
@near-js/keystores-node	Patch
@near-js/signers	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[andy-haynes]

Thanks @austinabell !