Add junit output to connectivity test

[brlbil]

Junit format varies from implementation to implementation. The below references were used as references.

https://github.com/windyroad/JUnit-Schema/blob/master/JUnit.xsd
https://llg.cubic.org/docs/junit/
k8s e2e junit output

--junit-file option is added to the connectivity test
test output is converted to junit xml format, and written to the destination file

Fixes: #281

[michi-covalent]

we should probably update our github workflows to write junit output right? are you planning to do it as a followup pull request?

[brlbil]

we should probably update our github workflows to write junit output right? are you planning to do it as a followup pull request?

I actually thought about adding a test but since cilium-cli tests run in the cluster I thought the output would not be very useful. Now I think we should add one even regardless of output is useful to test the functionality.

I think adding one of the tests is enough, what do you think @michi-covalent?

[michi-covalent]

I think adding one of the tests is enough

sounds good to me

edit:

maybe we can add the flag here => https://github.com/cilium/cilium-cli/blob/main/.github/workflows/kind.yaml#L152

[brlbil]

I missed the kind workflow, even better we can easily upload the connectivity test output with the kind workflow.
I will do this first thing tomorrow.

[viktor-kurchenko]

LGTM.

[michi-covalent]

xml ftw

[michi-covalent]

the button is too green not to click