Add javax Positive/Negative bean validation constraint support

[Neo1228]

Summary

• add support for javax.validation.constraints.Positive, Negative, PositiveOrZero, and NegativeOrZero in bean validation schema resolution
• map these annotations to OpenAPI numeric constraints (minimum/maximum and exclusiveMinimum/exclusiveMaximum)
• wire support in both group-aware and no-group validation flows in ModelResolver
• add regression-safe behavior so existing stronger bounds are not loosened

Details

• @Positive => minimum: 0, exclusiveMinimum: true
• @Negative => maximum: 0, exclusiveMaximum: true
• @PositiveOrZero => minimum: 0, exclusiveMinimum: false
• @NegativeOrZero => maximum: 0, exclusiveMaximum: false

When existing bounds are already stricter (for example @Min(5) with @Positive), the stricter bound is preserved.

Tests

• added integration test: BeanValidationTest
  • validates generated schema values for Positive/Negative/PositiveOrZero/NegativeOrZero
  • validates non-loosening behavior with stronger @Min/@Max
• expanded unit tests: ValidationAnnotationsUtilsTest
  • added tests for all four new utility methods
  • added tests that ensure existing stricter constraints are preserved

Commands run:

• mvn -pl modules/swagger-core "-Dtest=io.swagger.v3.core.resolving.BeanValidationTest,io.swagger.v3.core.util.ValidationAnnotationsUtilsTest" test
• mvn test -pl modules/swagger-core

[Neo1228]

Closing as duplicate of #5044 to avoid overlap.