New_EU_presets plus ham

[NomDeTom]

Some new presets for a wider range of operations in the EU, and a placeholder ham band. Relies on meshtastic/protobufs#824 for protobufs.

What has changed?

• 3 new region presets
  • EU_866,
  • NARROW_868, and
  • HAM_US433
• 4 new modem presets
  • LITE_FAST/SLOW,
  • NARROW_FAST/SLOW
• new region parameters
  • licensedOnly, to limit a region to ham operators, i.e. those operating with the licensed flag active
  • overrideSlots, to allow a region to always default to a particular slot
  • defaultPreset, to allow a default other than LongFast
  • availablePreset, to allow limiting preset availability to a particular region
• refactoring of the modem setting checks to happen before restarting the node
• adding additional client notifications for invalid setting combinations

What is needed to integrate these changes more widely

• BaseUI / InkHud
  • The new regions and presets have been added to the menu lists, but the list logic has not been updated to exclude invalid combinations
• MUI
  • The new regions and presets need to be added to the menu lists, and the list logic included.
• Client Apps
  • These will need updating to take account of the valid region/preset combinations, ideally hiding invalid combinations within the menus
  • Their display logic will need updating to include the new overrideSlots information, which will affect both the lora config menu and the behaviour when new primary channels are generated

Acknowledgements

This change has been supported extensively by @Stary2001, @phaseloop, and @caveman99. Their input cannot be understated.

🤝 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
  • LilyGo T-Deck
  • LilyGo T-Beam
  • RAK WisBlock 4631
  • Seeed Studio T-1000E tracker card
  • Other (please specify below)
    Pro-micro DIY

[NomDeTom]

@jp-bennett This PR now includes your custom CR check. Can you please re-check it in the context of this change? I don't know if we need additional logic to handle if moving to a preset with a higher default preset than the custom CR set, or indeed if we need to take account of people wanting to run CR4.

In any case, can you help me avoid a reversion of your change?