Remove node if VM doesn't exist even if computer is not idle

[Tyler-35]

When working with spot instance, when the agent is evicted/removed the node in jenkins is not removed because of this check which causes the build to hang.
If we move the idle check below the vm-exists check this solves the issue.

Testing done

Tested this change by adding more logging to see what was causing the issue of why the node wasn't being removed when the agent no longer existed.
The logging show it was being stop by the not idle check.
[FINE][com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask cleanVMs] Node cnp-jenkins-builderse8d030 is not idle, skipping
I next moved the idle check further down the code and tested removing the agent when the build was running. This time the clean-up task would remove the node.
[INFO][com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate virtualMachineExists] Checking VM exists for cnp-jenkins-builderse8d030 [INFO][com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate virtualMachineExists] cnp-jenkins-builderse8d030 doesnt exist [FINE][com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask cleanVMs] Node cnp-jenkins-builderse8d030 doesnt exist, removing

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[timja]

Hey Tyler,

I'm taking a look at this, in future please check out the submitter checklist, specifically this wasn't done:

Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!

(you've opened from your master branch)
Its easy to accidentally push unrelated changes to your master branch and affecting open PRs