feat(hono): Extend peer dependency range

[chargome]

• Extend optional peer deps to 2.x
• Move the e2e test to @hono/node-server@2, v1 is covered in integration tests

[sentry]

Bug: The peerDependencies range for @hono/node-server allows installing v2, which requires Node.js v20+, on projects using Node.js v18, causing runtime failures.
_{Severity: HIGH}

Suggested Fix

To prevent runtime failures on Node.js v18, either update @sentry/hono's engines field to require Node.js v20+, or restrict the @hono/node-server peer dependency to ^1.x to ensure only compatible versions are installed.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: packages/hono/package.json#L99

Potential issue: The `package.json` for `@sentry/hono` specifies a Node.js engine
requirement of `>=18`. However, it defines an optional peer dependency on
`@hono/node-server` with a version range of `^1.x || ^2.x`. Since version 2 of
`@hono/node-server` requires Node.js v20+, a user on a Node.js v18 environment could
inadvertently install this incompatible version. This will lead to a runtime failure
when the application attempts to import from `@hono/node-server`, as the package is not
compatible with Node.js v18.

Also affects:

• dev-packages/e2e-tests/test-applications/hono-4/package.json:21~21

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[chargome]

optional peer dep, that is fine. we'll bump to 20 in the next sdk major