Updated CI structure to increase coverage

[UebelAndre]

This change is related to #830

[UebelAndre]

This draft contains changes from the following PRs:

• Update //proto rules to provide all required dependencies. #868
• Minor cleanup of various tests and examples #869

[illicitonion]

This looks reasonable to me - I'd be tempted (though it's a big step) to maybe write a tiny python script to generate these, rather than writing them all manually, given at this stage we're building up a bit of a combinatorial explosion...

[UebelAndre]

This looks reasonable to me - I'd be tempted (though it's a big step) to maybe write a tiny python script to generate these, rather than writing them all manually, given at this stage we're building up a bit of a combinatorial explosion...

Yeah, but I don't feel like the jobs change so frequently that it's worth that kind of effort. If the issue is that the yaml is not that clear anymore, I'd ask for some pointers in yaml-fu before trying to write some generation tool 😄. Do you have any suggestions on that front?

[illicitonion]

This looks reasonable to me - I'd be tempted (though it's a big step) to maybe write a tiny python script to generate these, rather than writing them all manually, given at this stage we're building up a bit of a combinatorial explosion...

Yeah, but I don't feel like the jobs change so frequently that it's worth that kind of effort.

Fair! Now definitely doesn't have to be The Time.

If the issue is that the yaml is not that clear anymore, I'd ask for some pointers in yaml-fu before trying to write some generation tool 😄. Do you have any suggestions on that front?

In my experience, it's simply not possible to make yaml more readable :)

[UebelAndre]

@hlopko If there are no objections from you, I'd like to get this merged. I feel in general it's a good improvement

[hlopko]

I stand aside, feel free to merge :)