github: fix failing vagrant CI job

[gdams]

Checklist

• commit message has one of the standard prefixes
• faq.md updated if appropriate
• other documentation is changed or added (if applicable)
• playbook changes run through VPC or QPC (if you have access)
• for inventory.yml changes, bastillion/nagios/jenkins updated accordingly

fixes: #2425

This PR fixes the long-term failing Solaris Vagrant GH actions job. This was broken when we decided to switch to a custom vagrant image that was not available in the environment of the action. This PR switches that logic back to the public image for GH actions CI runs

[gdams]

@sxa any idea what the sudo error is complaining about? Looks like a missing library?

failed: [127.0.0.1] (item=nano) => {"ansible_loop_var": "item", "changed": false, "item": "nano", "module_stderr": "Shared connection to 127.0.0.1 closed.\r\n", "module_stdout": "ld.so.1: sudo: fatal: libpool.so.1: open failed: No such file or directory\r\nld.so.1: sudo: fatal: libpool.so.1: open failed: No such file or directory\r\nld.so.1: sudo: fatal: relocation error: file /usr/lib/libproject.so.1: symbol pool_conf_alloc: referenced symbol not found\r\nKilled\r\n", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 137}

[sxa]

It does indeed but I've not seen it before.

[zdtsw]

this probably is not needed after change done for getting solaris box file from /userContent

[zdtsw]

good to have this part

[karianna]

@gdams Vagrant build is still failing?