Default ADR does not take LoRaWAN version into account

[ghost]

What happened?

The default ADR algorithm does not take LoRaWAN version/region into account when adjusting TxPower, adjustments are always made in the 0-(maxTxPower according to band) interval.

If the device has sent a nACK on the TxPower this is stored in device session min/max but not taken into account when sending new adjustments.

Since the min and max will be adjusted, the process will calibrate itself but additional downlinks will be required after a "new" adjustment is made.

What did you expect?

When a device is registered as version 1.0.0 or 1.0.1 the applicable TxPower levels in EU868 is 1-5 and in later LoRaWAN versions the levels are 0-7.

Steps to reproduce this issue

1. Register a 1.0.0 or 1.0.1 sensor with enough link margin to trigger TxPower adjustments.

Component	Version
Network Server	v3.12.0