Support verify data in x mb

[GAllen98]

• A new type has been created to represent the data in x-mb from the manifest.
• Verify data can now be added to x-mb instead of being passed through flags on the command line

[bh2smith]

I see a lot of new stuff and no tests. I think this could be improved in a few different ways.

[SurgeCode]

If the new verify content is in the spec are we ingesting it on the wallet side as well? @GAllen98

[bh2smith]

Love the type validation! Thanks for including it. Might seem like a bit much to ask, but I was wondering if we might wanna test some of this code with real example?

The reason for having test fixtures in places like this prevent future devs from haphazardly breaking interface requirements that external parties might rely on. In some sense this is like "versioning" our specification and being able to determine when our specification changes are backwards compatible or introduce the need for a major version update. In fact, for our own sanity, we may even want to consider including a version tag on the structure so it's easier to parse older verses newer specs.

[bh2smith]

Nit: type guards usually follow the pattern

Example: https://github.com/BitteProtocol/near-safe/blob/6637da030c3f022029618c4993ec21be1cbaf655/src/types/guards.ts#L6

Suggested change

	export function validateXMbSpec(xMbSpec: unknown): asserts xMbSpec is XMbSpec {
	export function isXMbSpec(xMbSpec: unknown): asserts xMbSpec is XMbSpec {

Might also use data for input var name.

[bh2smith]

Also, type guards usually return true or false... in this case we return undefined when it passes all the assertions...

[bh2smith]

I added some tests on the validation as a PR based on this one.

May be a good starting point:

#42

Try it out with bun test.

In particular, the test demonstrates that the following object would pass validation:

{
    "account-id": "name",
    assistant: {
      name: "assistantName",
      description: "assistantDescription",
      instructions: "assistantInstructions",
  },
}