feat(builder): add strict validation to steps attributes

[mjlescano]

Closes https://linear.app/usecannon/issue/CAN-348/throw-an-error-if-you-have-stuff-in-your-operation-definition-thats

This PR does not allow to add invalid config values to step names, for example in [deploy.Contract] it would throw if you misspell artifact = as artifacttt =.

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 11ea4b2. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 1 target

• lerna run build --ignore cannon-website --ignore @usecannon/indexer --ignore repo --ignore @usecannon/api

---

Sent with 💌 from NxCloud.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 11ea4b2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[saeta-eth]

Overall looks good! As far as I can see, something went wrong in the inspect command on the e2e tests, it says something about "extras"...

[mjlescano]

The e2e tests are failing because the Synthetixio/synthetix-sandbox/cannonfile.toml#L119-L120 file has an error, using extras.* = * instead of extra.* = *. This is a good thing! But just to note that after we merge this PR all the existing cannon packages with typos are going to stop working.