Deployment should preserve daemon state

[tparchambault]

With the fapolicyd stopped initially, a successfully deployed modification to the Ancillary Trust DBase results in the fapolicyd's state changing to started/running. I believe that the analyzer's operations should have no side-effects beyond the requested operation, so in this particular case the eventual state of fapolicyd should be stopped. The user may have their reasons for wanting fapolicyd stopped. Conversely, if fapolicyd was running, after all analyzer operations are complete fapolicyd should be in the running state.

Note: the above example is an ATDB operation. Obviously, if the requested operation is to start or stop the Daemon then the requested operation should result in the daemon in that state.