chore(deps): update dependency vite to v8.0.10

…generation

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

…type

fix(plugin): handle IsIn enum inference when type falls back to Object

…Response decorators are present

PR #3803 added a guard that suppresses the auto-inferred default response
whenever any `Api*Response` decorator is present on a handler. The guard
doesn't distinguish success (2xx) from error (4xx/5xx) decorators, so a
handler with only `@ApiUnauthorizedResponse()` (or any other error-status
decorator) loses its auto-inferred 2xx in the OpenAPI spec. Downstream
client generators (NSwag, openapi-generator, ...) then treat the real
2xx response as an exception at runtime.

Scope the guard to decorators whose status code is below 400 so error
factories no longer suppress the default. The success/redirect case the
original PR fixed (`@ApiFoundResponse` on a `@Redirect()` handler)
continues to work — 302 is still below 400.

Status codes are derived from the decorator name via the same
`Api${PascalCase(HttpStatus key)}Response` convention the factories are
generated from in `api-response.decorator.ts`. Unknown names
(`ApiDefaultResponse`, user-defined) fall back to the previous behavior
(treated as explicit).

Closes #3862

…t/500 cases

Extend the fix so that a plain `@ApiResponse({ status: N })` is also classified
by its status code: a 4xx/5xx status no longer suppresses the auto-inferred 2xx.
Non-literal `status` expressions (e.g. `HttpStatus.OK`) can't be evaluated at
compile time and continue to be treated as explicit, preserving pre-existing
behavior.

Extend the regression fixture with:

  - `@Post @apiresponse({ status: 500 })` — asserts the default 201 is
    auto-added (the new arg-inspection case).
  - `@Get @reDIrect @ApiFoundResponse` — asserts no default is added, so the
    fix continues to honor #1639 for redirect handlers.

The existing `app.controller` fixture had baked in the 11.2.7 behavior on the
`create()` handler (multiple error-status `@ApiResponse` decorators); update it
to the restored pre-11.2.7 output (default 201 alongside the error entries).

…thod

Address PR review nit: move the standalone helper into ControllerClassVisitor
as a private method, since it's only used by addDecoratorToNode and doesn't
need its own module.

…orators-suppressing-default

fix(plugin): keep auto-inferred default response when only error Api*Response decorators are present