Mute: channels

[ford-jones]

Resolves #7943

Introduces mechanisms to mute message notifications received over specified channels.
When a message is received over a muted channel, the device's buzzer (if present) should not be activated. Drawing of any alert UI notification to the device's screen should also be blocked.

The exception to this is bell alerts (when activated), which should still sound the buzzer and display a notification.

• Buzzer always sounds when no channels are muted
• OLED popup always displays when no channels are muted
• When a specific channel is muted, messages received over that channel from any node don't invoke the buzzer
• When a specific channel is muted, messages received over that channel from any node don't display a popup

Protobuf changes: meshtastic/protobufs#769
Docs: meshtastic/meshtastic#2028

🤝 Attestations

• I have tested that my proposed changes behave as described.
• I have tested that my proposed changes do not cause any obvious regressions on the following devices:
  • Heltec (Lora32) V3
  • Seeed Studio T-1000E tracker card

[ford-jones]

There are two things left to be done here:

• Block message notification on InkHUD UI
• Block message notification on Meshtastic UI

I'm currently lacking the hardware to do this, I have some on the way but it's unlikely it will be here any time soon. If this PR is approved I will open a new issue for these TODOS which someone else can take up in the meantime - otherwise, I will do it when I have the hardware.

[garthvh]

Channels is fine, nodes is kind of a duplication of the existing ignore functionality.

[ford-jones]

Apologies, didn't mean to close/reopen.

@garthvh Happy to make changes, but I think it's worth considering that unlike ignore - the message is still delivered and can be read.

It should be noted that this behaviour is distinctly different to ignoring a node - an action which blocks the message entirely. Muted messages can still be viewed in the messages menu of the device or client application, they are just delivered discreetly.

[ford-jones]

After a discussion with @garthvh this morning; we've determined the best course of action here is to decouple muting nodes and muting channels into two seperate PR's.

This is to relieve pressure on the size constraint of the user proto - which currently hangs a big question mark over the ability to merge this.