Eliminate ConcurrentModificationException in free style projects

[mPokornyETM]

inspired by #558 and partly eliminates
see #503
see #601

The sense of this PR is to split the changes in mentiond PR #558 to make the review (and in worst case revert) much more simple.

note: dissallow white space check to eliminate many many changes produced by code formatting

Testing done

Didn´t creates new testcases. Current test cases shall be enough to validate this changes

Proposed upgrade guidelines

Logger priority in LRM for free-style projects has been changed.

Localizations

There are no UI relevant text.

Submitter checklist

• The Jira / Github issue, if it exists, is well-described.
• [ x] The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples).
  • The changelog generator for plugins uses the pull request title as the changelog entry.
  • Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during the upgrade.
• [ ] There is automated testing or an explanation that explains why this change has no tests.
• New public functions for internal use only are annotated with @NoExternalUse. In case it is used by non java code the Used by {@code <panel>.jelly} Javadocs are annotated.
• [ ] New or substantially changed JavaScript is not defined inline and does not call eval to ease the future introduction of Content Security Policy (CSP) directives (see documentation).
• [ ] For dependency updates, there are links to external changelogs and, if possible, full differentials.
• [ ] For new APIs and extension points, there is a link to at least one consumer.
• [ ] Any localizations are transferred to *.properties files.
• [ ] Changes in the interface are documented also as examples.