Improve lockable-resources build (job) page

[mPokornyETM]

Partly implement #667 with focus on performacne.
fix #703
The main change is to synchronized the addAction() per build and not global.
Also usage of getReadOnlyResources() is more or less obsolete, because all the actions provides in this plugin are synchronized correctly. That measn we spare a lot of memory and CPU by skipping the copy of all resources.

Testing done

My local tests (and also performance tests) looks fine

New LockableResources look on build page

tested also in #703

Proposed upgrade guidelines

N/A

Localizations

• English
• German
• French
• Slovak
• Czech
• ...

Submitter checklist

• The Jira / Github issue, if it exists, is well-described.
• 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 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.

[jimklimov]

Log message got sort of lost in conversion? Also below.