retry executing a scan on a node if azure responds with a conflict msg

[vjeffrey]

User Story

Sometimes Azure RunCommand jobs will respond with a conflict msg error noting that another job is already running on those nodes.
It would be nice if we could recognize this error, and upon receipt of it, wait about 60 sec and then retry. maybe we can have a 3 time retry, 60 seconds wait between each retry?
Let's play around with it and see how things go.

Definition of Done

Azure RunCommand nodes get a retry if conflict msg.

[vjeffrey]

Looks like we already have some code dedicated to retries here: https://github.com/chef/automate/blob/master/components/compliance-service/inspec-agent/remote/remote.go#L76 that handles aws throttling exceptions