Mark more errors as runner system failures

[tejassharma96]

Pull Request

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Build related changes
• Documentation content changes
• Other: (describe here)

Proposed Change

Issue Number: #28

Update several more errors that occur while starting up the VM as runner system failures, rather than reporting them as script failures

Breaking Change?

Maybe? Depends on how/whether people have set up alerting on runner system failures for their anka executors, but they will see more of those with this change. It doesn't break any functionality, so imo this is not a breaking change.

Checklist

Please validate that your PR fulfills the following requirements:

• I have branched from the default repo branch (can be master, main, or release/vX.X)
• I have checked that a similar PR does not exist or has been rejected in the past
• PR changes are specific to a feature or bug
• No style/format/cosmetic changes included
• I have used existing style and naming patterns in my changes
• Tests for the changes have been added/updated (if relevant)
• Built/compiled and tested locally
• Docs have been added/updated (if relevant)
• I have squashed my changes into a single commit

Additional Information

[github-service-user-veertu]

Can one of the admins verify this patch?

[NorseGaud]

github-service-user-veertu run build

[tejassharma96]

FYI despite my initial thought in slack that everything in prepare.go should be a runner system error, I left the check for the template uuid/name verification as script failures, since really that indicates that there is something wrong with the gitlab ci configuration rather than something going wrong in the runner. I'd be fine updating those to be runner system failures too though, I am not strongly opinionated (for specifically that case, I am opinionated about these other ones 😅)