MaintenanceTool Does Not Distinguish Between Standard and Static Boot2Qt QBSP Packages

I have noticed an issue with the Qt MaintenanceTool when installing and managing Boot2Qt QBSP packages built with different configurations. Specifically, the MaintenanceTool currently does not distinguish between standard (dynamic) and static Boot2Qt QBSP packages.

After building a Boot2Qt SDK with PACKAGECONFIG += "static" (to generate static Qt libraries), I installed the resulting QBSP via the MaintenanceTool. However, when both standard and static QBSPs are present (either installed side-by-side, or switching between them), the MaintenanceTool does not show any indication of which package is static and which is dynamic. This leads to confusion and the potential to overwrite or mix up different types of toolchains/environments.

Expected Behavior

When building a static SDK (with PACKAGECONFIG += "static"), the resulting SDK, image, and QBSP should be clearly marked as static in the MaintenanceTool UI and installation metadata—much like other Qt variants such as wasm-singlethreaded versus wasm-multithreaded in the official online installer.

Suggestion

Maybe this change could be handled within the meta-boot2qt layer and/or the QBSP configuration/build process to ensure static SDKs and images are properly marked. For example, including an explicit label or tag for static packages in the QBSP manifest, filename, and display name shown in MaintenanceTool would make it much easier to distinguish between static and dynamic builds.