feat: add exclusiveMinimum and exclusiveMaximum

[jefflembeck]

Add @exclusiveMinimum and @exclusiveMaximum JSDoc annotations for strict inequality bounds (> / <), complementing @minimum/@maximum (>= / <=).

Spec output follows each OpenAPI version's JSON Schema draft:

• Swagger 2.0 / OAS 3.0: boolean form (minimum: X, exclusiveMinimum: true)
• OAS 3.1: numeric form (exclusiveMinimum: X)

When both @Minimum and @exclusiveMinimum are present, v2/v3.0 errors; v3.1 emits both.

Closes #1842

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you written unit tests?
• Have you written unit tests that cover the negative cases (i.e.: if bad data is submitted, does the library respond properly)?
• This PR is associated with an existing issue?

Closing issues

Put closes #XXXX (where XXXX is the issue number) in your comment to auto-close the issue that your PR fixes.

If this is a new feature submission:

Potential Problems With The Approach

• @Minimum and @exclusiveMinimum (or @maximum/@exclusiveMaximum) cannot coexist in Swagger 2.0 and OAS 3.0
  because exclusiveMinimum is a boolean modifier on minimum in those spec versions. This PR throws at spec
  generation time if both are used together in 2.0/3.0. In OAS 3.1 they are independent numeric values and
  can coexist.
• Runtime validation enforces both validators independently — there is no runtime conflict check for
  combining minimum + exclusiveMinimum, since the spec generators already prevent this for 2.0/3.0 and it's
  valid in 3.1.

Test plan

• Unit tests (templateHelpers.spec.ts): 8 tests covering exclusiveMinimum and exclusiveMaximum for both
  integer and float validation — verifying values above the bound pass, and values equal to the bound are
  correctly rejected (the boundary condition for exclusive semantics).
• Spec generation unit tests: Tests in definitions.spec.ts (Swagger 2.0), schemaDetails3.spec.ts (OAS 3.0),
  and schemaDetails31.spec.ts (OAS 3.1) verify correct schema output per spec version — boolean form for
  2.0/3.0, numeric form for 3.1 — and that combining @Minimum + @exclusiveMinimum throws in 2.0/3.0 but
  succeeds in 3.1.
• Integration tests: All five server integration suites (express, hapi, koa, koa-no-additional,
  dynamic-controllers, openapi3-express) updated to validate that requests with
  exclusiveMinimum/exclusiveMaximum fields pass on valid input and return the correct error messages on
  boundary values.