Use git cherry-pick (git rebase also works) to sync with the OM code

See our tracking issues under the OM label for list of changes that need to be processed

• Keep the authorship and sign-offs of the original commits
• Skip or remove all OM's binary files (e.g. *.bin, *.mwm etc.) as they're covered by OM's proprietary binary data license
• Add original commits SHAs (from OM's repo) to PR description in a git log --oneline format (example)
• Label OM cherry-picking PRs with the OM label
• Keep cherry-picking history so that we know what had been picked already, what had been discarded, what needs to be considered for picking, etc. in issues like https://codeberg.org/comaps/comaps/issues/1373 (keep updated the first post there and add any picked commits and respective PRs as separate posts)
• Fix-ups (excluding merge conflict resolves) and adaptations (e.g. modifying icon to use CM colors) should be done in a separate commit of your authorship
• When preparing release notes mention the original author and that it came from OM (e.g. Fixed ... - by @vng via OM)