build: ship files_lock with 34

[blizzz]

Summary

We want to ship files_lock auto-enabled with 34.

Requires / needs:

• build: build and commit frontend assets from 34 on files_lock#1068
• enh: files_lock will be shipped as of NC 34 github_helper#150

ToDos

• backport second commit (updatenotification) to stable33

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

AI (if applicable)

• The content of this PR was partly or fully generated using AI

[blizzz]

Opened as draft as some other bits and pieces have to fall into place (see description)