Bumps [actions/setup-node](https://github.com/actions/setup-node) from 4 to 6.
- [Release notes](https://github.com/actions/setup-node/releases)
- [Commits](actions/setup-node@v4...v6)

---
updated-dependencies:
- dependency-name: actions/setup-node
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [hono](https://github.com/honojs/hono) from 4.9.7 to 4.10.2.
- [Release notes](https://github.com/honojs/hono/releases)
- [Commits](honojs/hono@v4.9.7...v4.10.2)

---
updated-dependencies:
- dependency-name: hono
  dependency-version: 4.10.2
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Update the zValidator wrapper with the latest polymorphic/backwards compatible types from
`@hono/zod-validator` 0.7.4. Try hard to not rely on `any`. Type check the code with `tsc` during
linting to catch errors.

I'm not personally a fan of how `@hono/zod-validator` is typed. This may be a situation, however,
where TypeScript's verifier can't exhaustively check things because of the lack of higher-kinded
types. I think the solution is for them to provide overloads for v3 and v4 zod schemata and make the
 innards of the function very vague about types.

Signed-off-by: Alexandra Parker <alexandra.i.parker.civ@us.navy.mil>
Co-authored-by: Alexandra Parker <alexandra.i.parker.civ@us.navy.mil>

Comment out the samples update step in CI workflow

…2472)

* fix(core): added possibility to explicitly mark dependencies as namespace imports

* fix(zod): fixed bug where zod did not correctly use namespace import

Co-authored-by: melloware <4399574+melloware@users.noreply.github.com>