Pin bcutil-fips to stabilize Maven dependency resolution (#1323)
## Summary
- Pin `org.bouncycastle:bcutil-fips` to `2.1.8` in the parent POM's
dependency management. This is the version Maven already selects when
the range resolves.
- Remove the need to fetch the version list to resolve the
`[2.1.7,2.2.0)` range from `bctls-fips` and `bcpkix-fips`. Its
resolution failed intermittently in [the documentation
PR](https://github.com/OpenIdentityPlatform/OpenDJ/actions/runs/44906503870/job/136853123526)
and [on
master](https://github.com/OpenIdentityPlatform/OpenDJ/actions/runs/44887182636/job/136794952463).
## Validation
- Reproduced the CI error on `opendj-core` with Maven 3.9.15 and Java 11
using an isolated Maven repository containing the JAR and missing the
`bcutil-fips` version metadata. The same check passed with the pin and
resolved the same four FIPS artifacts as the baseline with metadata.
- Ran `mvn --batch-mode --offline --file opendj-core/pom.xml verify` on
Java 11. All 8,261 tests passed.
- Ran `git diff --check`.