Dynamic channel configuration on NO-IR for requested channel

[joshschmelzle]

Some regulatory domains do not allow Tx on channel 36, but do in higher U-NII-3 bands. In this case, the default channel configured will not allow Profiler to work. This can cause some issues with starting Profiler from FPMS or the WebUI as we do not have channel selection baked into either of those interfaces.

Consider adding the ability for Profiler to check if the requested channel to launch Profiler on has the ability to Tx. If no, check for and use a different channel in the same band if possible.

Potentially the selection criteria looks like this:

• Check Tx for 36 (default channel).
• If no channels enabled for Tx, check U-NII-3 first.
• If no Tx channels in U-NII-3, check any other channel.

Other notes:

• This logic should be expanded to 6 GHz as well. Start at channel 5 PSC which should work for most if not all regulatory domains.
• Do not add fall back logic to a different band as that changes what is being profiled.
• Consider a custom exit condition for when there is no available channel to Tx on. This could be consumed by FPMS and WebUI (probably via wlanpi-core).