add buildkite upload

[finn-tbd]

and re-arranged some stuff:

• split out all report renders to their own file
• update result struct to track per-test runtime
• disable failing web5-kt test
• use web5-js test from web5-js repo, drop web5-js test from this repo
• renamed the go package to reflect the current repo name

[andresuribe87]

@finn-tbd just wanted to make sure you didn't miss https://github.com/TBD54566975/sdk-development/pull/68#pullrequestreview-1751550533

tl;dr; should all the code in here be tested? Apologies if it's being tested already and I missed it.

Otherwise this lgtm

[finn-tbd]

@andresuribe87 this is all tested, most of it in the branch's CI:

• junit (new template) is rendered and sent to buildkite in CI because the token is present (results here)
• md is rendered and written to the github summary (link to rendered md from the most recent pipeline)
• text is rendered and displayed in the Github Actions text output (bottom of "self test" job from this pipeline)
• html template i tested locally

edit: unless you're talking about more automated correctness verification like unit tests or something. I don't feel those are necessary right now, especially with the desire to increase our velocity, but if others disagree I'm open to looking at ways to unit test the templates.

[andresuribe87]

edit: unless you're talking about more automated correctness verification like unit tests or something. I don't feel those are necessary right now, especially with the desire to increase our velocity, but if others disagree I'm open to looking at ways to unit test the templates.

I was talking about those automated tests. I'd expect things to be really easy to test if you already have samples. I would argue not having them decreases our velocity in the medium term, as modifications to anything in the upload pipeline will be hard to verify.