release_versions endpoint - lts vs non-lts versions breaks jdk8u info https://release-monitoring.org/project/371025/

**Describe the bug**

Unclear API expectations for `lts=true` vs `lts=false` - this might be an API issue or it might be an issue that needs to be fixed on the release-monitoring side.

I was looking at the release_versions endpoint as that seems used by release monitoring https://release-monitoring.org/project/371025/ and noticed it didn't contain the last 2 jdk8u updates https://wiki.openjdk.org/display/jdk8u/Main 8u422-b05 and 8u412-b08 (report 8u402+6)

**To Reproduce**
Steps to reproduce the behavior:
1. Compare the outputs of the following

```console
curl 'https://api.adoptium.net/v3/info/release_versions?&page=0&page_size=100&project=jdk&release_type=ga' | jq ' .versions[] | select(.major == 8) '
```

The above results in empty output

```console
curl 'https://api.adoptium.net/v3/info/release_versions?&page=0&page_size=100&project=jdk&release_type=ga<s=true' | jq ' .versions[] | select(.major == 8) '
```

```json
{
"adopt_build_number": 1,
"build": 5,
"major": 8,
"minor": 0,
"openjdk_version": "1.8.0_422-b05",
"security": 422,
"semver": "8.0.422+5.1"
}
...
```

**Expected behavior**

It looks to me like the 8 LTS releases only appear with lts=true but I assume at some point in the past they were there without for the fedora release-monitoring service to pick up.

I assume jdk8u432 will appear under the lts releases once the adoptium version is tagged built (only got tagged on openjdkk/jdk8u half an hour ago). But I'm wondering if those releases being missing without lts=true is expected (as there probablyy needs to be a separate release-monitoring entry for adoptium-openjdk-lts setup

Start by comparing the two release_versions curl requests in the issue and inspect the release-monitoring project and OpenJDK jdk8u references it links. The payload names no source files or tests; done means establishing the expected lts=true versus lts=false behavior for JDK 8 releases and documenting or correcting the API/release-monitoring handling accordingly.

Written by the indexing model from the issue text.