Improve boolean labeling for operation inputs

[Matti2603]

This commit is part of this issue: #538

As part of the "Software Engineering" course at DHBW Stuttgart, a student team is working on this issue under the supervision of @mrentsch65

https://github.com/DHBW-TINF24F/Team2-BaSyx-Viewer-Plugin-Erweiterung

Description of Changes

This pull request improves the labeling of boolean input variables in Operation submodules.

Boolean values are now displayed more clearly in the UI using visual switches and explicit true/false labels. This makes boolean operation inputs easier to understand and improves the usability of Operation submodules.

Related Issue

#538

BaSyx Configuration for Testing

No special configuration is required. The feature can be tested with the standard frontend setup and a running BaSyx backend.

AAS Files Used for Testing

A test AAS file containing an Operation submodel with boolean input variables was used to verify the improved boolean labeling.

The test file contains boolean inputs such as:

• enableMachine
• emergencyStop
• maintenanceMode
• automaticRestart
• enableDataLogging

Testing

• Tested with an AAS containing an Operation submodel
• Verified that boolean input variables are displayed as switches
• Verified that true and false states are visible in the UI
• Checked that non-boolean input variables are not affected

[aaronzi]

Thanks for the PR. Please remove the .DS_STORE file and sign the Eclipse contributor agreement with the same mail that you used for your commit.

[Matti2603]

removed ds_store and signed the agreement.

[aaronzi]

There seems to be atleast one commit that was made with another email:

mattifrey@MacBook-Ai*-von-Matti DOT local

Could you please check that. You could either cherry-pick that commit or open a new PR with the same changes again but only contributed via the "correct" mail.

Also please fix linting errors (e.g. pnpm run lint:fix)