Optionally skip AWT/JVM runtime libraries for Tao-only GraalVM packages

[BruceZhang1993]

⚠️ Is your feature request related to a problem? Please describe

Tao is documented as removing the AWT/Swing window hierarchy and its native libraries, but GraalVM packages still include AWT/JVM runtime libraries such as "libjvm", "libawt", and "libfontmanager".

The current GraalVM packaging tasks bundle these libraries by default, including for applications using only "decorated-window-tao" and "NucleusBackend.Tao".

For Tao-only applications this adds a significant amount of unnecessary runtime data to the package.

Related documentation:
https://nucleusframework.dev/en/docs/tao/migration-from-jbr/

💡 Describe the solution you'd like

Make bundling the AWT/JVM companion libraries an explicit GraalVM packaging option instead of the default behavior.

Applications that need AWT or other JDK native libraries could enable the option, while Tao-only applications could package without them.

🤚 Do you want to develop this feature yourself?

• Yes
• No

[kdroidFilter]

It is true that the graphical rendering no longer depends on AWT. Nevertheless, AWT is still necessary for Compose to function properly, for example for clipboard access, or when using Jewel, which relies heavily on libfontmanager.

I understand the request to make it opt-in, but I think that would be quite dangerous, as it could lead to bugs that would be extremely difficult to track down. So I remain fairly skeptical about this approach.

[BruceZhang1993]

AWT is still necessary for Compose to function properly, for example for clipboard access

@kdroidFilter That makes sense. In my case, I use the Tao gtk clipboard instead of Compose's AWT-backed clipboard.

So my use case is mainly an experimental opt-out option for applications that have tested and verified the AWT fallback is not needed.