Don't scale up the frequency of telemetry sending

[RCGV1]

Previously if the num online nodes was lower than a certain amount our node would send telemetry at a higher interval than configured, this leads to congestion in scenarios where a node has a bidirectional mesh connection where it doesn't see many nodes but transmits well. It is also not typical for a setting to be used more like a suggestion, the broadcast interval should be a minimum interval.

Related issues:
#8649
#8619

[fifieldt]

This patch makes sense. It might be worth checking what the firmware implemented hard minimum limit is and making the minimum a bit more flexible in small networks? Just to make sure there isn't someone out there relying on this we're cutting off.

[thebentern]

The original purpose of scaling down the coefficient was to not hamstring small off-grid and backpacking networks into the same coarse broadcast interval constraints as large public ones

[RCGV1]

I think we should let the user have more decision over the interval especially now that you have to manually enable it.

[RCGV1]

I don't think that for a hiking network you would need to know clients battery percent less than every 30 min