User requests the ability to select between various amplified modules (Power Amplifiers) in userspace via a configuration protobuf. This would simplify supporting different EBYTE modules and hardware revisions by allowing appropriate Tx power curves to be programmed without extensive sub-environments.
### Platform NRF52, Cross-Platform ### Description I would like to introduce a configuration protobuf (I am guessing a struct) to select between various amplified modules to program in the appropriate Tx power curve. This would greatly simplify the proliferation of many different sub-environments needed to support various EBYTE modules, for example, and possibly different hardware revisions of products like Heltec v4 which may use different FEMs between hardware revisions. E.g. this would simplify the XIAO nRF sub-variants that exist for E22-900M22S, E22-900M30S, E22-900M33S. Additionally, a build-time define like LORA_PA_OPTIONAL for example, should clamp the Tx power to 0dBm (which still transmits, albeit weakly) for safety (avoid burning the PA) until a PA (or explicitly selecting that there is no PA e.g. E22-900M22S) is specified. I bring this up now because I don't feel like we should continue expanding variants to add E22-915M30P, E22-915M33P, which also have different cur