Refactor setLock() and getLock()

[danielb987]

@dsand47
I have earlier added the methods getLock() and setLock(), but I have never used them. But the way these was implemented wasn't so good. So I have refactorized these methods by moving them from the interface jmri.jmrit.logixng.Base to jmri.jmrit.logixng.MaleSocket.

This PR will have a conflict with #9864 that I will resolve once #9864 is merged.

TreeEditor works with female sockets and male sockets, so TreeEditor has access to the methods getLock(), setLock() and isSystem(). The idea is that the user can lock and unlock a node and I think it would be good if that would lock/unlock all the nodes in the sub tree of that node as well.

If a male socket is system (the method isSystem() returns true), then it would be good if the user gets a dialog box asking for confirmation when he tries to edit, cut or delete a node.

The method setSystem() is intended for ImportConditional when importing system Logixs and if a JMRI tool creates internal LogixNGs for its own use.

[mergeable]

Thanks for the PR. Please consider adding a release note in the help/en/releasenotes/current-draft-note.shtml file.

[mergeable]

Thanks for the PR. It includes changes to properties files, so the 'Needs L10N' label has been added"

[codecov]

Codecov Report

Merging #9866 (7eaea3d) into master (a185c38) will increase coverage by 0.1%.
The diff coverage is 41.8%.

@@             Coverage Diff             @@
##             master    #9866     +/-   ##
===========================================
+ Coverage      51.7%    51.7%   +0.1%     
- Complexity    64220    64221      +1     
===========================================
  Files          5112     5112             
  Lines        446298   446379     +81     
  Branches      64477    64518     +41     
===========================================
+ Hits         230682   230750     +68     
+ Misses       192837   192820     -17     
- Partials      22779    22809     +30     

Impacted Files	Coverage Δ
java/src/jmri/jmrit/logixng/Base.java	77.3% <ø> (-2.1%)	⬇️
java/src/jmri/jmrit/logixng/MaleSocket.java	65.0% <ø> (ø)
...ri/jmrit/logixng/actions/AbstractAnalogAction.java	93.4% <ø> (-0.7%)	⬇️
...i/jmrit/logixng/actions/AbstractDigitalAction.java	100.0% <ø> (ø)
.../logixng/actions/AbstractDigitalBooleanAction.java	100.0% <ø> (ø)
...ri/jmrit/logixng/actions/AbstractStringAction.java	93.4% <ø> (-0.7%)	⬇️
.../logixng/expressions/AbstractAnalogExpression.java	88.3% <ø> (-1.2%)	⬇️
...logixng/expressions/AbstractDigitalExpression.java	100.0% <ø> (ø)
.../logixng/expressions/AbstractStringExpression.java	88.3% <ø> (-1.2%)	⬇️
...t/logixng/implementation/AbstractFemaleSocket.java	75.4% <ø> (-1.0%)	⬇️
... and 55 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a185c38...7eaea3d. Read the comment docs.

[coveralls]

Coverage increased (+0.01%) to 56.862% when pulling 7eaea3d on danielb987:lock_unlock into a185c38 on JMRI:master.

[danielb987]

@dsand47
I have implemented Lock/Unlock in this PR.

If an item is locked, a lock icon is shown before that node.

If the user selects "Lock" on an item, that item and all its descendants are locked.
If the user selects "Unlock" on an item, that item and all its descendants are unlocked.

An item can be edited, enabled and disabled if it's not locked.

An item can be added if the parent is not locked. An item can be cut or removed if it's not locked and its parent is not locked.
.

This may seem difficult, but my idea is:

• If the item is locked, it should not be possible to change that item (it's settings, username, local variables, ...) or to remove it (cut, remove).
• If the parent is locked, it should not be possible to reorder its children or to add or remove its children.

---

I have added a warning dialog if the user tries to edit/cut/remove a system item. You can test this by changing system="no" to system="yes" in the panel file. With system, I'm referring to things like Logix RTX and SYS, that is items that are created and maintained by JMRI itself.

[danielb987]

@dsand47
This PR is ready for review.

[dsand47]

Looks good. I assume it is ok to unlock a child.