Move properties into separate package

[TheAssassin]

This cleanup makes working with them more convenient.

Counterpart of t-oster/VisiCut#725.

[mgmax]

Looks good.

• Please resolve conflicts - I can't click the merge button otherwise :-)
• Can you do some testing to make sure that this does not break loading old VisiCut settings?
  • Suggestion: In the previous VisiCut version, create several laser devices and save some material settings, so that you have XML laserprofile files for each of the property classes that are moved (PowerSpeedFocusFrequencyProperty, ..., whatever). Then look that in the new version you still see the old values.
• Once this is merged, you can update the PR in VisiCut so that it also includes the new version of the LibLaserCut submodule, and then we can merge that too.

[TheAssassin]

• Conflicts resolved
• Test confirms that the move itself does not break anything

Edit: it's no wonder, given the structure of the XML files, that moving packages does not break anything:

<linked-list>
  <PowerSpeedFocusProperty>
    <power>100</power>
    <speed>80</speed>
    <focus>0.0</focus>
  </PowerSpeedFocusProperty>
</linked-list>

[TheAssassin]

I suggest you merge this PR, then I can update a variety of others.

[mgmax]

The tests fail because you deleted one Java file. Please try again :)

[TheAssassin]

Somehow, rebasing in this repository is my arch nemesis. Anyway. Let's try again.

[TheAssassin]

Here we go.

[mgmax]

Thanks :-)