"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.

Comienza en tools/script_manager.lua, en el callback del botón disable_scripts; después inspecciona la preferencia para deshabilitar los scripts de Lua y la ruta de carga de luarc incluida en darktable 5.6. Reproduce el comportamiento con los scripts incluidos habilitados y determina si se debe eliminar el botón o hacer que alterne la preferencia. Se considera terminado cuando deshabilitar los scripts mediante el módulo de scripts impide realmente que se carguen los scripts incluidos, y el camino para volver a habilitarlos sigue siendo claro.