Updating the control example by adding option to make Table and Tree Widgets editable

[ShahzaibIbrahim]

Updating the example by adding option to make Table and Tree Widgets editable

This commit is part of testing the custom controls for multi-monitor support.

HOW TO TEST

• Run the Runtime Workspace launch configuration
• Open the SWT Controls view
• Switch to the tab "Tree"/"Table"
• Check the "Editable" option under "Other"
• Edit the content of the tree/table

Contributes to #62 and #127

[github-actions]

Test Results

   478 files  ±0     478 suites  ±0   6m 47s ⏱️ - 2m 41s
 4 137 tests ±0   4 129 ✅ ±0   8 💤 ±0  0 ❌ ±0 
16 341 runs  ±0  16 249 ✅ ±0  92 💤 ±0  0 ❌ ±0 

Results for commit 92ad33f. ± Comparison against base commit 80086c9.

♻️ This comment has been updated with latest results.

[fedejeanne]

@ShahzaibIbrahim thank you for this contribution!

It looks good, just one detail: you don't need to add the controls to the SWT Custom Controls view since they are already in the SWT Controls view.

Please base your PR on top of master instead of akoch-master-33 to improve testability,

I changed the "How to test" in the description of this PR since manual testing is also testing

[fedejeanne]

Last detail and then this PR is OK

[HeikoKlare]

I have two remarks on this:

1. Please format the code. There is currently a mixture of whitespace-based and tab-based indentation. Applying the auto-formatting to the changed/added code should result in proper indentation.
2. Please adapt the commit message (in particular the title) to contain what the PR does and not what it might be used for. Currently the title is "Provide HiDPI Support for Multi-Monitor Environments for custom controls" but I do not see anything related to HiDPI support in the PR. Such information can be useful in the PR description, to make it easier for reviewers to understand use cases, and maybe also in the commit message, but the commit title (i.e., the first line of the commit message) should capture what the commit does and not what it might be used for.

Once these issues are addressed, I think we can also merge these improvement during freeze period as it only affects examples code that is not shipped with the SDK (just like we are allowed to still improve tests).

[HeikoKlare]

Unfortunately, you have now applied some auto-formatting to the complete classes, so the commit is full of unrelated formatting changes. Please revert those formatting changes and only format the code that you have edited/added.

I addition, please ensure that the commit title fits into a single:

New errors were introduced

[ShahzaibIbrahim]

Unfortunately, you have now applied some auto-formatting to the complete classes, so the commit is full of unrelated formatting changes. Please revert those formatting changes and only format the code that you have edited/added.

@HeikoKlare I have applied formatting now only on my changes also changed the commit message

[HeikoKlare]

I have some further comments on code complexity and code style.

[HeikoKlare]

Thank you for the contribution and for addressing my comments! The code looks good now. And the changes still work as expected.

[HeikoKlare]

Merging, since freeze period check only fails because of M1 promotion calendar entry, but merging is actually allowed (and the change does not affect production code anyway).