fix: exclude bridge methods from @JsonValue enum detection (#5127)

[olsavmic]

Summary

Fixes #5127 — @JsonValue on an enum implementing a generic interface (e.g. PersistableEnum<String>) causes non-deterministic schema generation in OpenAPI 3.1 mode.

Root cause

When an enum implements a generic interface like PersistableEnum<T>, the Java compiler generates a bridge method Object getValue() alongside the real String getValue(). The compiler copies @JsonValue to the bridge method.

ReflectionUtils.getAnnotatedMethods() uses getDeclaredMethods() without filtering bridge methods, so both methods are returned. In ModelResolver._createSchemaForEnum(), findFirst() picks whichever getDeclaredMethods() returns first — which is unspecified per JVM spec.

• If String getValue() wins → PrimitiveType.fromType(String.class) → schema with type: "string" ✓
• If Object getValue() (bridge) wins → PrimitiveType.fromType(Object.class) → null → falls through to default

This causes non-deterministic output: the same code produces different schemas across JVM invocations (e.g. Maven Surefire vs IntelliJ test runner).

Fix

One-line change in ReflectionUtils.collectAnnotatedDeclaredMethods() to skip bridge methods:

if (!method.isBridge() && method.isAnnotationPresent(annotation)) {

Tests added

• ReflectionUtilsTest.getAnnotatedMethods_excludesBridgeMethodsFromGenericInterface — verifies only the non-bridge method is returned
• EnumPropertyTest.testJsonValueWithBridgeMethodFromGenericInterface — end-to-end: enum with generic interface gets correct type: "string" and enum values
• New test model classes: PersistableEnum<T> interface and JacksonValueBridgeMethodEnum enum