Creating annotations for failed e2e tests

[xt0rted]

Checklist:

• If this PR is a new feature, please provide at least one example link
• Make sure all of the significant new logic is covered by tests

I split this out of #1035 since it's not related to that piece of work.

I'm wondering if we should take a dependency on actions/core so we can use their issueCommand function which handles building & escaping everything.

[stefanbuck]

I'm wondering if we should take a dependency on actions/core so we can use their issueCommand function which handles building & escaping everything.

I like the simplicity of the console.log, but you made a good point. I think this is something we can look into in separate PR. This is already a huge improvement. Thanks for looking into this.

[staabm]

To support multi-line messages you need to encode \n with %0A

See mheap/phpunit-github-actions-printer#14

[xt0rted]

@stefanbuck looks like switching to console.log() doesn't work as expected. Some messages get written out, but others don't because of how the tests are async but not everything is awaited.

https://github.com/OctoLinker/OctoLinker/pull/1048/checks#step:10:51

I tried making everything async but the callback to describe() can't be async so I'm back to square one now.