doc: releases: 3.7: change of hawkbit autohandler

Mention change of hawkbit autohandler and shell in the
migration guide and the release notes.

Signed-off-by: Fin Maaß <f.maass@vogl-electronic.com>

doc/releases/migration-guide-3.7.rst

@@ -322,6 +322,9 @@ hawkBit
   * :kconfig:option:`CONFIG_SETTINGS` needs to be enabled to use hawkBit, as it now uses the
     settings subsystem to store the hawkBit configuration.
 
+  * :c:func:`hawkbit_autohandler` now takes one argument. This argument has to be set to
+    ``true`` for the same behavior as before the change.
+
 LoRaWAN
 =======
 

doc/releases/release-notes-3.7.rst

@@ -299,6 +299,25 @@ Libraries / Subsystems
       registered to set the device attributes that are sent to the hawkBit server. Use the
       :c:func:`hawkbit_set_custom_data_cb` function to register the callback.
 
+    * :c:func:`hawkbit_autohandler` now takes one argument. If the argument is set to true, the
+      autohandler will reshedule itself after running. If the argument is set to false, the
+      autohandler will not reshedule itself. Both variants are sheduled independent of each other.
+      Both variants are run in the system workqueue.
+
+    * With :c:func:`hawkbit_autohandler_wait` you can wait for the autohandler to finish. This
+      function will block until the autohandler is finished. As ``event`` parameter you can pass
+      ``UINT32_MAX`` to wait for the autohandler to finish one run or use :c:macro:`BIT`
+      together with a value of c:enum:`hawkbit_response` to wait for a specific event.
+
+    * The run of hawkBit from the shell has been reworked to be executed in the system workqueue.
+      So it will run in the same thread as the hawkBit autohandler.
+
+    * Use the :c:func:`hawkbit_autohandler_cancel` function to cancel the autohandler.
+
+    * Use the :c:func:`hawkbit_autohandler_set_delay` function to delay the next run of the autohandler.
+      If the parameter ``if_bigger`` is set to true, the delay will only be set if the new delay is
+      bigger than the current delay.
+
 * Logging
 
   * By enabling :kconfig:option:`CONFIG_LOG_BACKEND_NET_USE_DHCPV4_OPTION`, the IP address of the