FP in trivy because of confusing sha1 info in trivy java db

I see several issues in java db that all together causes a FP in trivy and need to be handled in the trivy-java-db and in trivy...
1. in the latest fetched trivy java db I see that the latest version of kaml is missing in the db. version 0.53.0 was released on 18.3.2022. the question why is it missing... maybe because of next item
2. as you can see https://repo1.maven.org/maven2/com/charleskorn/kaml/kaml/0.52.0/kaml-0.52.0.jar.sha1 and https://repo1.maven.org/maven2/com/charleskorn/kaml/kaml/0.53.0/kaml-0.53.0.jar.sha1. The two versions have the same sha1... I wonder how can this be.... and this is leading to next item
3. in case we try to scan kaml-0.53.0.jar and because the only entry in the java db for the sha1 1464f167409b1df8aa89b1630f06036b71872b7a is for 0.52.0, and because the file does not have version info, we query the db for the sha1 and get version 0.52.0 and report CVE-2023-28118 for version 0.53.0 which was fixed in 0.53.0 as stated in https://nvd.nist.gov/vuln/detail/CVE-2023-28118

Start by reproducing a scan of kaml-0.53.0.jar and comparing the SHA-1 records for versions 0.52.0 and 0.53.0 in trivy-java-db and trivy. Done means the database includes the released version and Trivy does not identify 0.53.0 as 0.52.0 or report CVE-2023-28118 against it.

Written by the indexing model from the issue text.