fix(tests) fix test expectations due to package-level variable

[michaelbeaumont]

Summary

In these two tests we can't contact the API server and so the warning is printed by the compiled kumactl. This line

https://github.com/michaelbeaumont/kuma/blob/1333e7c965a15bed2527cf69977931021add4c35/app/kumactl/cmd/root.go#L79

is being hit and thus we aren't initializing kumaBuildVersion, but kumaBuildVersion is nevertheless != nil. With FIt we can see that whether we run the other tests determines if these pass or fail.

Full changelog

• fix(tests) fix test expectations due to global variable

Testing

• Unit tests
• E2E tests
• Manual testing on Universal
• Manual testing on Kubernetes

Backwards compatibility

• Add backport-to-stable label if the code is backwards compatible. Otherwise, list breaking changes.

[jakubdyszkiewicz]

I think we should get rid of this check in config cmd. So commands like kumactl config add do not throw warnings. If you are messing around with config it is expected that you don't have a connection to the control plane yet

[michaelbeaumont]

@jakubdyszkiewicz makes sense actually, closing for #2828