[Kotlin/Native] 标识细分

[jackhb1999]

这是现有的标识，支持 [Kotlin/Native] ，但是实际上我是使用的时候：

能不能像 amper 一样支持到 Native 的具体平台。这对于依赖的选择、使用会更加方便。

[berezinant]

Thanks for the suggestion jackhb (@jackhb1999) !

Just to better understand your expectations, could you elaborate a bit more on what an ideal solution would look like for you?
Also If you have a concrete example (e.g., how this should look in the UI or filters), that would be very helpful

[jackhb1999]

Thanks for the suggestion @jackhb1999 !感谢你的建议 @jackhb1999！

Just to better understand your expectations, could you elaborate a bit more on what an ideal solution would look like for you?为了更好地了解您的期望，您能否再详细说明一下，对您而言理想的解决方案是什么样的？ Also If you have a concrete example (e.g., how this should look in the UI or filters), that would be very helpful另外，如果你有具体的示例（例如，这在界面或筛选器中应该是什么样子），那将非常有帮助。

当前保留的：
JS
JVM
ANDROID_JVM
需要细分的：
WASM_JS
WASM_WASI

Kotlin/Native的细分，或许要有二级tag，当然用以下tag取代kn的tag
LINUX_X64
LINUX_ARM64
TVOS_ARM64
TVOS_X64
TVOS_SIMULATOR_ARM64
MACOS_X64
MACOS_ARM64
IOS_ARM64
IOS_SIMULATOR_ARM64
IOS_X64
WATCHOS_ARM64
WATCHOS_ARM32
WATCHOS_DEVICE_ARM64
WATCHOS_SIMULATOR_ARM64
MINGW_X64
ANDROID_NATIVE_ARM32
ANDROID_NATIVE_ARM64
ANDROID_NATIVE_X64
ANDROID_NATIVE_X86

总之，我认为细化kn的平台有利于开发者的使用和kn的完善，tag那么多，lib开发的大佬也许会想集齐的。

当然这个细化，寻找各个平台的依赖是否分发可能有点难，我还没找到比较好的klib仓库。

或许 https://github.com/JetBrains/amper/blob/main/sources/frontend-api/src/org/jetbrains/amper/frontend/platform.kt 的区分，用树形选择怎么样