Use nav-tabs in the resources page

[mPokornyETM]

When you use many resources and many labels, the page /lockable-resources/ might have a long content. Scroll down after every refresh to see labels-status is not very user friendly.

This PR will provide a view in nav-tabs. It is also prepared for futured tabs like log and queues.

Many thx to Vandit Singh @Vandit1604

Testing done

Just few manual tests.
Used Jenkins 2.361.4

Proposed upgrade guidelines

N/A

Localizations

• English
  Other localizations shall be provide by Crowdin

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.
• Any localizations are transferred to *.properties files.

Maintainer checklist

Before the changes are marked as ready-for-merge:

• Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
• Proper changelog labels are set so that the changelog can be generated automatically. See also release-drafter-labels.
• If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
• java code changes are tested by automated test.

[mPokornyETM]

@g3n35i5 or @mark-reiche maybe you can review this changes

[mark-reiche]

@mPokornyETM reviewed the change and tested it manually here. Looks good to me.

[chickenkiller]

very nice ! Thank you, great improvement!