Convert AnsibleEntity and SaltEntity to be real SoftwareProcess

[tbouron]

Background

Salt and Ansible are currently installed by Brooklyn and:

• are used in masterless mode
• use SSH to check their health
• but more importantly, are used to install and manage software. For instance, using Salt, one can install and start/stop Apache or Nginx (or any other software). The same applies to Ansible.
  They are effectively software processes as they manage software lifecycle but are not considered as such based on their current implementation.

Issue

The current implementation uses EffectorStartableImpl instead of SoftwareProcessImpl. This has some side effects which might be surprising for users, such as:

• the inboundPort (provisioning.properties) are not applied when the SG is created (on supported clouds)
• the auto-opening port on SG by creating config keys finishing by .port does not works
• the shell.env are also not applied (BROOKLYN-503)
• if the location is using a machine name customiser, this will throw a NPE as the CALLER_CONTEXT is not set

This list is not exhaustive, I just wanted to illustrate the most common issues a user will bump into by using those entities.

Solution

Make those 2 entities real SoftwareProcesses, this PR is doing just that. I simply moved around the existing code to make it match the phases of SoftwareProcess.

This has been tested with YAML tests available here for Ansible and here for Salt

[drigodwin]

LGTM, thanks @tbouron