[nrf fromlist] drivers: clock_control nrf_lfclk: patch clock option order

[bjarki-andreasen]

The clock options used within the driver are supposed to be ordered from lowest to highest power consumption, so the lowest/default option is the most power efficient. The order was reversed to make the init code of the lfclk a bit simpler, and this was accounted for in the clock option lookup function. However, the common nrf clock control request/release feature would request the lowest index, not the lowest clock option, so the lfclk would default to its highest power consumption mode.

The clock option init and lookup has been refactored to be sorted from lowest to highest power consumption, and comments have been adjusted accordingly.

Upstream PR #: 99382

[nordic-piks]

Works fine at CI:

13:33:53  INFO    - 1/2 [email protected]/nrf54h20/cpuapp benchmarks.multicore.idle_clock_control.app PASSED (device: 001051180995, 40.903s <zephyr>)
13:33:53  INFO    -                                    benchmarks.multicore.idle_clock_control.app.test_measure_and_data_dump_power_consumption_clock_control PASSED
13:34:06  INFO    - 2/2 [email protected]/nrf54h20/cpurad benchmarks.multicore.idle_clock_control.rad PASSED (device: 001051100381, 39.155s <zephyr>)
13:34:06  INFO    -                                    benchmarks.multicore.idle_clock_control.rad.test_measure_and_data_dump_power_consumption_clock_control PASSED

[karl-nordic]

@bjarki-andreasen Side task:
LFXO startup time. {*startup_time_us = dev_data->lfxo_startup_time_us;}
Is it anyhow used by clock controller ? Some time ago, there was discussion that this parameter is not utilized by anyone.
The conclusion from the dissuasion was to not use this parameter in BICR. It will be there, but customers will just not fill it.
Is that an issue for clock control ?

[carlescufi]

@bjarki-andreasen Side task: LFXO startup time. {*startup_time_us = dev_data->lfxo_startup_time_us;} Is it anyhow used by clock controller ? Some time ago, there was discussion that this parameter is not utilized by anyone. The conclusion from the dissuasion was to not use this parameter in BICR. It will be there, but customers will just not fill it. Is that an issue for clock control ?

Note that @bjarki-andreasen is off for two weeks, so this will have to wait