Remove 'latest' key from index.json for itext metadata

[vitali-pr]

Starting from 8.0.4 itext core includes reachability metadata into library.

What does this PR do?

Looking at https://www.graalvm.org/native-image/libraries-and-frameworks/ it seems there is a redundancy in terms of supported versions of itext core libs. I believe removing 'latest' key from index.json should remove '8.0.3 - latest' range from the page above and leave only 8.0.3. Though I don't see any similar example in the whole repo so not sure.

Checklist before merging

• I have considered including reachability metadata directly in the library or the framework (see our contributing document)
• I am the original author of all content provided in the pull request, and I did not copy the content from any other source (see the tests section from our contributing document)
• For all tests where I am not the sole author, I have added a comment that proves I may publish them under the specified license (see the tests section from our contributing document)
• I have properly formatted metadata files (see our formatting guide)
• I have added thorough tests (see the tests section from our contributing document)
• I have filled all places where my pull request accesses files, network, docker, or any other external service (see the section above)

[vitali-pr]

@msupic , it's hanging for quite some time already. Could you, please have a look?

[msupic]

@dnestoro - I will not have time to review this so if you or somebody else can review it would be great.

[dnestoro]

I am not sure what to do in this case. @fniephaus since you are more familiar with libraries-and-frameworks list, what do you think?

[fniephaus]

Thanks for bringing this to our attention, @vitali-pr. I'm not sure we really need to change the metadata but the changes you suggest look reasonable to me. Anyway, it will not automatically solve the double listing on the graalvm.org website. Let me take a look next week and see how we can improve the website. Maybe this change is actually not needed, in which case it may be better to delay the changes until they are really needed. :)

[fniephaus]

LGTM, thanks! We are going to update the website very soon

[fniephaus]

We have improved the website and it now shows, for example, this: