Add summary for executable verbs

[matipan]

Add a summary for all verbs that run commands. The summary includes the actual dagger command that was executed, a link to the trace and the output of dagger version. For example:

[jedevc]

SGTM, I'm just conflicted on whether we actually want this as the default.

e.g. if users want to generate their own job summaries, this is actually quite annoying.

Alternatively:

• What if we had an input that was a file path to write the report to?
• What if we had an output that was a file path / raw content of the report?
  Then we can control the format and magic generation of the report, while allowing user control over what actually happens to the report.

[matipan]

That's fair. I haven't really used summaries much. A quick search for a few examples seems like they usually have two options: one for specifying where to write the summary and another one to specify whether to automatically add it to GitHub actions. For example: https://github.com/marketplace/actions/super-linter#summary-outputs. I would do both options as well. So that its easy to automatically add summaries to github without more work than setting an option @jedevc