Add RISC-V platform support in discoapi

[gounthar]

Following issue sdkman/sdkman-cli#1321, I propose to add the RISCV64 architecture to discoapi.

• Add riscv64 architecture to ARCHITECTURE_MAP in src/main/java/io/foojay/api/distribution/Temurin.java.
• Update getUrlForAvailablePkgs method to include riscv64 in src/main/java/io/foojay/api/distribution/Temurin.java.

Summary

• New Features
  • Added support for the RISCV64 architecture in the architecture mapping, enhancing the capability to handle a broader range of architectures for package requests.

Walkthrough

The changes introduced in this pull request involve the addition of a new architecture, RISCV64, to the ARCHITECTURE_MAP within the Temurin class. This update includes mapping the RISCV64 architecture to the string representation "riscv64", allowing the Temurin class to support RISC-V 64-bit architecture in URL parameters. No other modifications to logic or error handling were made, ensuring that the existing functionality of the class remains unchanged.

Changes

File Path	Change Summary
src/main/java/io/foojay/api/distribution/Temurin.java	Added RISCV64 to ARCHITECTURE_MAP, mapping to "riscv64".

[HanSolo]

The RiscV64 pkgs from Temurin are already available...please check for example this: https://api.foojay.io/disco/v3.0/packages?distribution=temurin&latest=available&release_status=ga&architecture=riscv64&jdk_version=23

[gounthar]

Thank you for the feedback.

I initially thought my proposed changes would resolve this SDKMan! issue. I now understand that adding riscv64 to the Temurin class was not necessary.

I apologize for the confusion. I'm still learning how the system handles architectures without explicit definitions. Could you help me understand this better?

[HanSolo]

SDKMan gets all OpenJDK and GraalVM distributions from discoapi. But that doesn’t mean they provide all architectures etc. that disco offers.

[gounthar]

Closing this PR; as @HanSolo pointed out, the Disco API already serves riscv64 packages without needing an explicit mapping in the distribution classes.

The actual missing piece is in sdkman-disco-integration, which needs to recognize riscv64 as a platform. That's now tracked in sdkman/sdkman-disco-integration#45 with PR sdkman/sdkman-disco-integration#46.

Thanks for the explanation on how architecture resolution works!