See commit 3f345ecb
Rename tree_resolve_copy and tree_resolve_master_copy to
tree_resolve_sanitize and tree_resolve_master_sanitize respectively.

At write time:
  - Add the whole sa to the new cdb field named sa instead of storing the key one by one.
  - Store uniquely the uint of the key instead of appending a string.

At read time:
  - Do not build again the sa looking for the cdb value but read the whole sa instead.
  - Do not use extra HEAP memory allocation.
At modification time:
  - Sanitize the resolve by writting the sa from scratch.
  - Use /tmp directory as temporary cdb file.
Replace resolve_find_cdb by the resolve_get_key and resolve_get_sa function.
Replace service_resolve_copy by service_resolve_sanitize.

Each tool needs to be independent, which
meant that every time a tool was called,
it would build the entire system graph.
This was an obvious waste of time and resources.

Now, the tools build the graph based
on the requested services, which
drastically reduces the time needed to
construct the necessary dependency graph.

This program is executed via the run script in the service's live directory. It sits between s6-supervise and the user's executable script, allowing for the preparation of the user's script execution. This introduces a dual capability:

    Define certain preparations through frontend keys, such as setting ownership, moving to a working directory, limiting resources used by the service, etc.
    Since 66-execute runs on each signal received and transmitted by s6-supervise, it is now possible to send messages to an event management daemon.

By default, this program performs previously defined actions such as logging redirections and managing environment variables (previously handled by excel-envfile), creation of the log destination directory, and so on.So, the user's file now contains only the exact copy of the @execute field.
Also, the name of the script for an start or
stop process are the same. This was a old behabvior
coming from s6-rc  manager.

This reverts commit 87bd69c6.

Service may not be supervised, in this case the ssexec_stop function do not find the service to remove and its requiredby dependencies and refuse to remove the service. Whatever the state of the service, the service must be removed.