feat: better YAML parsing error reporting

[fbricon]

Description

When config.yaml doesn't conform to the expected schema, the reported error is somewhat cryptic. This PR adds zod-validation-error to render more user-friendly error messages (until prettifyError() becomes available in the next zod 4.0)

Checklist

• I've read the contributing guide
• [] The relevant docs, if any, have been updated or created
• [] The relevant tests, if any, have been updated or created

Screenshots

Before:

After:

Tests

• Added packages/config-yaml/src/load/unroll.test.ts
• To test manually, add this snippet to your config.yaml (name property is missing):

data:
  - destination: http://localhost:3000

---

Summary by cubic

Improved YAML config error messages by using zod-validation-error, making validation issues easier to understand.

• Dependencies
  • Added zod-validation-error and updated zod to 3.24.4.

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[netlify]

✅ Deploy Preview for continuedev ready!

Name	Link
🔨 Latest commit	7f60f16
🔍 Latest deploy log	https://app.netlify.com/projects/continuedev/deploys/682d9b657fb51f0008c21182
😎 Deploy Preview	https://deploy-preview-5750--continuedev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[fbricon]

With zod 3.24.4, required by zod-validation-error, compilation fails with:

Argument of type 'ZodObject<Pick<{ eventName: ZodString; schema: ZodString; userId: ZodString; userAgent: ZodString; selectedProfileId: ZodString; } & { ...; }, "timestamp" | ... 29 more ... | "disableInFiles">, "strip", ZodTypeAny, { ...; }, { ...; }> | ... 7 more ... | ZodObject<...>' is not assignable to parameter of type 'AnyZodObject'.
Type 'ZodObject<Pick<{ eventName: ZodString; schema: ZodString; userId: ZodString; userAgent: ZodString; selectedProfileId: ZodString; } & { ...; }, "timestamp" | ... 29 more ... | "disableInFiles">, "strip", ZodTypeAny, { ...; }, { ...; }>' is not assignable to type 'ZodObject<any, any, any, { [x: string]: any; }, { [x: string]: any; }>'.
Types have separate declarations of a private property '_cached'.

If someone can come up with a better solution than this fugly hack, I'll be glad to apply it.

[RomneyDa]

@fbricon Wondering if this is because zod isn't updated in core?

[fbricon]

@RomneyDa you're exactly right, nice catch. I set "zod":"^3.25.13" consistently and could remove
that hack.

[RomneyDa]

looks good, appreciate the tests. See comment!

[RomneyDa]

@fbricon it seems like this is actually failing tests, something with the updated package locks maybe?