ci: compile on CI after merge to reduce conflicts and total CI time

[susnux]

Summary

One of the biggest CI problems we currently face are conflicts, not within source code but in compiled assets.
So if you have 2 PRs targeting e.g. files then the assets will likely conflict even if the source can be merged without problems.

This causes unnecessary CI time and developer frustration.

Another really bad example: Dependency updates.

So this solution is the currently lived solution of the text app:

1. we add a CI check to forbid checking in compiled assets
2. we adjust the node workflow to no longer check for asset changes
3. we add a CI workflow to compile after merges.

For the corner case where a new PR is merged before the compilation has finished this will abort the first compile and start a new one for the current HEAD.
So this also reduces the repository size in cases of many quick merged like during dependabot updates.

TODO

⚠️ this needs some repository setups ⚠️

1. This needs to be aligned with the releases team, during releases:

• either you compile in the PR and force merge with red CI for the "forbid assets" check
• or you merge and wait for the compile to finish to tag the release

2. This needs setup of the secrets to be able to push the compiles assets

• Setup a github environment update-node-dist
• Setup secret BOT_GITHUB_TOKEN with push permission to the branches
• ❗ see text repository setup for how to do this securely

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