FEAT(client): Add separate notification types for image messages

[28arnab]

The client currently treats messages containing embedded images as regular text messages for logging and notification purposes. That makes it impossible to disable notifications for image posts without also disabling notifications for normal text messages.

This commit keeps image delivery on the existing TextMessage protocol path but classifies incoming messages with embedded content as image messages in the client. It also adds dedicated log/settings entries for image messages and private image messages so their notifications can be configured independently.

Implements #6970

Checks

• My commits follow the commit guidelines

[coderabbitai]

Walkthrough

This pull request introduces two new message types—ImageMessage and PrivateImageMessage—to the logging system. These types are added to the Log::MsgType enum and integrated throughout the codebase with corresponding string conversions, localization entries, and sound settings. The MainWindow::msgTextMessage handler now detects whether incoming text messages contain image embeds by checking for the "<img" substring and logs them using the new message types accordingly. System tray notifications for these messages are configured to display without an icon.

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description provides clear context for the change, explains the problem it solves, describes the implementation approach, and references the related issue. The required checklist item is marked as completed.
Title check	✅ Passed	The title clearly summarizes the main change: adding separate notification types for image messages, which directly reflects the introduction of ImageMessage and PrivateImageMessage log types across all modified files.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/mumble/Messages.cpp`:
- Around line 1040-1046: The current substring check in Messages.cpp
(messageContent/hasImage/msgType selection) is too loose and case-sensitive;
include QRegularExpression and replace the contains(QLatin1String("<img")) check
with a case-insensitive regex match for an actual <img tag boundary (e.g.
pattern "<img\\b") using QRegularExpression::CaseInsensitiveOption so tags like
"<IMG>" match but tokens like "<imgur>" do not, then compute hasImage from that
regex match and keep the existing msgType selection logic (use privateMessage,
Log::PrivateImageMessage, Log::ImageMessage, etc.).

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 71342437-65a2-48d7-8766-5f90cd12c5b4

📥 Commits

Reviewing files that changed from the base of the PR and between 22f331f and addccfa.

📒 Files selected for processing (5)

• src/mumble/EnumStringConversions.cpp
• src/mumble/Log.cpp
• src/mumble/Log.h
• src/mumble/Messages.cpp
• src/mumble/Settings.cpp

[28arnab]

@Hartmnt can you check ? my last pr for this issue got removed by me because i followed ai to fix a git issue.

[Hartmnt]

You can start by squashing the two relevant commits and then dropping the merge commit. Then rebase against the current master branch. We want to have PRs without merge commits. (force push is the correct way to update this PR)

I have not tested if this works, yet. But this PR will most likely not make the cut for 1.6 anyway.