chore: publish CI test results

[alexec]

Signed-off-by: Alex Collins [email protected]

Don't bother creating a PR until you've done this:

• Run make pre-commit -B to fix codegen, lint, and commit message problems.

Create your PR as a draft.

• Your PR needs to pass the required checks before it can be approved. If the check is not required (e.g. E2E tests) it
  does not need to pass.
• Once required tests have passed, you can make it "Ready for review".
• Say how how you tested your changes. If you changed the UI, attach screenshots.

Tips:

• If changes were requested, and you've made them, then dismiss the review to get it looked at again.
• Add you organization to USERS.md if you like.
• You can ask for help!

[github-actions]

Unit Test Results

    6 files      5 suites   59m 3s ⏱️
365 tests 361 ✔️ 4 💤 0 ❌

Results for commit 6d89965.