Test reporter in Lucy (berkeley)

[dkijania]

Explain your changes:

Introduced test reported module, which is responsible for converting test executive log into junit.xml format which then can be consumed by buildkite test analytics module: https://buildkite.com/docs/test-analytics#main. I had to make some changes in Lucy code as well to correctly determined what is test result. For this purpose I've added new log level (Span), which is a common way to inform reader that about inner scope of logs.

Currently only junit.xml is supported (preferred was buildkite json file, but buildkite api has issues on uploading.. resolving it with buildkite support team).

Link to rfc: https://github.com/o1-labs/rfcs/pull/15

Checklist:

• [ ] Modified the current draft of release notes with details on what is completed or incomplete within this project
• [ ] Document code purpose, how to use it
  • Mention expected invariants, implicit constraints
• [ ] Tests were added for the new behavior
  • Document test purpose, significance of failures
  • Test names should reflect their purpose
• [ ] All tests pass (CI will check this if you didn't)
• [ ] Serialized types are in stable-versioned modules
• [ ] Does this close issues? List them

[dkijania]

!ci-build-me

[dkijania]

!ci-build-me

[dkijania]

!ci-build-me

[dkijania]

!ci-build-me

[dkijania]

!ci-build-me

[dkijania]

!ci-build-me

[dkijania]

!ci-build-me

[dkijania]

!ci-build-me

[dkijania]

!ci-build-me

[dkijania]

!ci-build-me

[dkijania]

!ci-build-me

[dkijania]

!ci-build-me

[dkijania]

!ci-build-me

[dkijania]

This PR is required to satisfy test executive reporting to buildkite. Thanks to test reported we can upload test results to bk and it will contribute to overall test execution graph in test module in bk