"disable scripts" in script manager needs update for 5.6

Description
The disable scripts button in the scripts module renames <config_dir>/luarc to luarc.disabled (the disable_scripts button callback in tools/script_manager.lua). This worked before the scripts were bundled, when darktable used <config_dir>/luarc as the Lua entry point.

Since 5.6, darktable loads the bundled luarc, which calls require "tools/script_manager" regardless of config_dir/luarc existing or not. Renaming config_dir/luarc no longer disables the scripts. It only prevents the user's own config_dir/luarc from being re-run. The bundled scripts still load and start.

Steps to reproduce

use darktable 5.6 with bundled scripts.
scripts module / action: install/update scripts / enable "disable scripts" button / click disable scripts.
observe luarc being renamed in the config dir

Restart darktable.

Expected: the Lua scripts are disabled.
Observed: bundled scripts still load and run.

Possible fixes
The current way to disable the scripts is the disable Lua scripts preference.
a) have the button toggle the disable_scripts preference (with the checkbox as the re-enable path)
b) remove the button in favour of the preference

I'd favour the latter - then enabling/disabling lua scripts is reduced to the preferences.

Commencez dans tools/script_manager.lua, au niveau du callback du bouton disable_scripts, puis examinez la préférence de désactivation des scripts Lua et le chemin de chargement de la luarc fournie dans darktable 5.6. Reproduisez le comportement avec les scripts fournis activés et déterminez si le bouton doit être supprimé ou s’il doit basculer la préférence. C’est terminé lorsque la désactivation des scripts via le module de scripts empêche effectivement le chargement des scripts fournis, tout en laissant clair le chemin pour les réactiver.