Disable fm-api service as part of install stage

Immediately after the system installation, fm-api service tries to
start and fails because it needs some files generated during the
bootstrap stage.
With this commits the service remains loaded, and the enabling happens
during bootstrap stage.

Test plan:
PASS: * Deploy a system until the install stage.
      * Check that fm-api.service did not fail and remains in
        loaded state.

Depends-on: https://review.opendev.org/c/starlingx/ansible-playbooks/+/866990
Closes-bug: 1999267

Signed-off-by: Agustin Carranza <agustin.carranza@windriver.com>
Change-Id: I3d4ffc66e742797453532f22479d7e960a128d3f

base/systemd-presets/source/stx/systemd/traits/aio.preset

@@ -17,7 +17,7 @@ enable controllerconfig.service
 enable uexportfs.service
 
 # 00-fm-rest-api.preset
-enable fm-api.service
+disable fm-api.service
 
 # 00-haproxy-config.preset
 disable haproxy.service

base/systemd-presets/source/stx/systemd/traits/controller.preset

@@ -17,7 +17,7 @@ enable controllerconfig.service
 enable uexportfs.service
 
 # 00-fm-rest-api.preset
-enable fm-api.service
+disable fm-api.service
 
 # 00-haproxy-config.preset
 disable haproxy.service

base/systemd-presets/source/stx/systemd/traits/lowlatency.preset

@@ -17,7 +17,7 @@ enable controllerconfig.service
 enable uexportfs.service
 
 # 00-fm-rest-api.preset
-enable fm-api.service
+disable fm-api.service
 
 # 00-haproxy-config.preset
 disable haproxy.service