[FEATURE] release smoke test++

[rvolosatovs]

Is your feature request related to a problem? Please describe.
In #616 a simple smoke test was added for releases executing the binary on all runners and simply killing it after a timeout to ensure it did not crash. Would be great to extend it a bit and rather than just killing after timeout, perhaps do some curl calls to the API and/or fetch wash binary and use wash to interact with the server

Describe the solution you'd like
curl it or wash it, whatever we do, it should be fast, i.e. 1 minute is the top threshold of how long this whole process can take per binary

[brooksmtownsend]

I like the idea of curling the dashboard to ensure a response, and then using wash to query the inventory of the host or start a really small actor.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this has been closed too eagerly, please feel free to tag a maintainer so we can keep working on the issue. Thank you for contributing to wasmCloud!