s32k14x canbootloader:Change autobaud to ACK and range high to low

[davids5]

When only this device was on bus not ACK's would be sent and device could not autobaud.

94ee6d3 Solves #22068

But there is still an issue with APP not taking the boot baudrate and Node ID. from the bootloader.

• The s32k bootloader was not actually writing the Node ID and bit rate.
  s32k14x:Make use of boot_app_shared shared_[un]lock] cc31daa Solves this.

• Once the Node ID and bit rate was written, the Nuttx SocketCAN driver was wiping out the values.
  This is solved with:
  boot_app_shared:Add optional board_app_shared_read f8fe64b
  UavcanNode:Support optional board_app_shared_read 5e9624e
  nxp_ucans32k146:Provide board_app_shared_read 33afff4

• The node was changing addreses.
  s32k14x:canbootloader board_identity Return the same word ordering as the s32k1xx/version/board_identity is solved by abef56d

• Then SocketCAN was broken by 3d61ab8
  SocketCAN uses FDs. FD's are per task/thread Run() is not on the same thread as init().

@AlexKlimaj Please test this branch with your use cases.

• added rgbled_ncp5623b

• Nuttx's s32k1cc_lpi2c driver Needed to not allow 0 delays

~~@vincentpoont2 I will need the current application source code for DroneCan F9P ~~

I will need to round trip the nuttx change and repoint this.

Nuttx Backports added

[davids5]

Rebased on current main. Nuttx Updated to tip with backports

[davids5]

@dagar, @AlexKlimaj Please have a look

[AlexKlimaj]

Tested the bootloader and app on the ARK Cannode with an ARKV6X and the Dronecan gui as the node ID server. Looks like its working.