Add ClassResolverCache for valid constructor lookup

[MessiasLima]

Description

Create a ClassResolverCache to cache valid constructor lookup results used by ClassResolver. This should reduce repeated reflection and constructor-selection work when the same classes are resolved multiple times.

Scope and constraints

• Preserve constructor declaration order and first-success behavior.
• Preserve fallback from failed constructors to later constructors.
• Do not cache generated constructor arguments or instantiated objects.
• Account for requested generic types, default-value strategy, property factories, and constructor failures when determining cache validity.
• Preserve existing circular-reference and instantiation-exception behavior.

References

• core/src/main/kotlin/dev/appoutlet/some/resolver/ClassResolver.kt
• core/src/test/kotlin/dev/appoutlet/some/resolver/ClassResolverTest.kt
• Related issue: Rename DataClassResolver to ClassResolver and support multiple constructors #46
• Related issue: Cache resolver lookups in ResolverChain #116

Scope

Add ClassResolverCache, integrate it with ClassResolver, and add tests verifying constructor-cache reuse and behavior preservation.

Out of scope: changing constructor ordering, constructor argument-generation rules, resolver precedence, or the public Resolver API.

Acceptance criteria

• ClassResolverCache stores and returns valid constructor lookup results for supported classes.
• Repeated resolution of the same compatible class reuses cached constructor information without repeating the full constructor-discovery process.
• Constructor selection continues to use declaration order and returns the first constructor that succeeds.
• If a constructor fails, later constructors remain eligible and existing fallback behavior is preserved.
• Cache entries do not incorrectly reuse constructor selections across incompatible generic types or configuration contexts.
• Existing behavior for private constructors, empty constructors, default parameters, property factories, circular references, and SomeInstantiationException remains unchanged.
• Tests verify cache reuse, constructor fallback, cache isolation, and existing failure behavior.