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

@@ -333,6 +333,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

@@ -300,6 +300,20 @@ 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.
+      The autohandler always runs in the system workqueue.
+
+    * Use the :c:func:`hawkbit_autohandler_wait` function to wait for the autohandler to finish.
+
+    * Running hawkBit from the shell is now executed in the system workqueue.
+
+    * 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.
+
 * Logging
 
   * By enabling :kconfig:option:`CONFIG_LOG_BACKEND_NET_USE_DHCPV4_OPTION`, the IP address of the