Improve handling of ssh-agent process

[Sn0wCrack]

Fixes #22

Currently I have the following added to all of my workflow files using the deployerphp action for our self hosted runners:

- name: Clean Up SSH Agent
  if: always()
  run: |
    killall ssh-agent
    rm ~/.ssh/config

This works fine, however recently we had started having multiple runner instances on each of our runner servers and conflicts began to arise with my solution due to the usage of killall

While I could have improved killing off the ssh-agent, I've decided to take a crack at implement a way of handling the ssh-agent process a little more nicely within the action iteself and have ended up with this.

There is probably a slightly better way of doing this via a proper setting, however I was aiming for backwards compatibility where possible.

---

What this PR does:

1. Spawns the SSH agent without specify a socket path, ensuring a unique socket path for each runner.
2. Adds a new option to toggle if the action should disable strict host checking if no known hosts are provided.
3. Adds a cleanup task that ensures all SSH keys are removed from the SSH Agent.
4. Ensures the SSH is shutdown on the runner server.

Why make these changes:

1. Improves supports for self hosted runners while also adding a bit of extra security for those using GitHub hosted runners.
2. Allows for the action to still handle the SSH related tasks for the end user without actually touching anything SSH related if necessary.
3. Probably doing things "the right way", so to speak, in that we're cleaning up after ourselves as part of the action.

[antonmedv]

Thanks for PR. Let's merge it but with little bit changes.

[Sn0wCrack]

Thanks for PR. Let's merge it but with little bit changes.

Thanks for the consideration, what changes did you have in mind here?

[antonmedv]

Different naming and default. Not running ssh=agent instead of killing.

[Sn0wCrack]

Different naming and default.

Do you have any suggestions for these?

Not running ssh=agent instead of killing.

The main reason I'm still running ssh-agent in my scenario is because deployerphp itself cannot read in a private key from a string and requires it to be a file on the system.
Instead of attempting to create the key file and have to clean that up I found it easier to just continue to use the ssh-agent process and remove all the keys from the ssh-agent process and kill it.

I could put the "cleanup" step behind an additional flag so it only kills off the ssh-agent process if you pass through another option telling it to.

I should note killing the ssh-agent process does cleanup the socket file as well.

[Sn0wCrack]

I'm just circling back to this PR after a bit, is this still something you'd be interesting in merging @antonmedv?