Fixes: #494

* Add the following properties into the mentioned file:

- `Automatic-Module-Name`
- `Implementation-Title`
- `Implementation-Vendor`
- `Implementation-Vendor-Id`
- `Implementation-Version`

Fixes: #496

The `RecoverAnnotationRecoveryHandler` occasionally invokes an unexpected `@Recover`
method when more than one candidate is a valid match.
The outcome depends on the order of `Class#getDeclaredMethods()`, which is not
specified by the JVM.
In real builds this shows up as flaky tests or different behavior between
JDK distributions/OS-es.

* When multiple `@Recover` candidates exist, choose the most specific and
deterministic handler instead of relying on reflection order.

Signed-off-by: Chih-Yu Huang <selina221947@gmail.com>

Bumps [org.assertj:assertj-core](https://github.com/assertj/assertj) from 3.27.3 to 3.27.7.
- [Release notes](https://github.com/assertj/assertj/releases)
- [Commits](assertj/assertj@assertj-build-3.27.3...assertj-build-3.27.7)

---
updated-dependencies:
- dependency-name: org.assertj:assertj-core
  dependency-version: 3.27.7
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

See gh-502

See gh-503

Closes gh-503

Closes gh-502

This commit improves RetryContextCache implementations to work in an
additional LRU mode that ensures the cache capacity does not prevent
updates to existing entries and automatically evicts older entries
rather than rejecting new contexts when the capacity is reached. A
warning is logged when capacity is breached instead of throwing an
exception.

Additionally, to prevent a stateful retry cache leak from polluting
the global circuit breaker cache, two separate caches are now used.
For global state cache, the existing implementation is used, throwing
an exception when the capacity is reached. For others, regular stateful
retry cache, a cache with LRU mode is used.

When using @EnableRetry, a unique `RetryContextCache` bean is applied
to regular stateful retries. To configure the circuit breaker's
cache specifically, a bean named `circuitBreakerRetryContextCache`
must be provided. To configure both independently, beans named
`retryContextCache` and `circuitBreakerRetryContextCache` can be
defined.

Closes gh-505