ci: fix mergify matrix integration tests

[mhofman]

Description

Mergify can get stuck when matrix tests fail, not realizing that the PR cannot make forward progress anymore.

This change reports a matrix job result as normal job, and switches mergify to using that job's result instead

Security Considerations

None

Scaling Considerations

None

Documentation Considerations

None

Testing Considerations

Will manually test variations on this PR

Upgrade Considerations

None

[michaelfig]

Why not go all the way, and have a single integration-result? Is there something I'm missing?

Then most of this logic can collapse into just:

    - or:
          - label=bypass:integration
          - check-success=integration-result
          - check-neutral=integration-result
          - check-skipped=integration-result

[mhofman]

Yeah I guess. I had tried that before, but with the wrong if condition. This should work just as well

[mhofman]

Done. I also removed the label=bypass:integration because that label being applied will caused the result job to be skipped, and makes the logic for mergify simpler to realize the condition has no other way to succeed.

[michaelfig]

Very pretty and squeaky clean! Just one question, but I'll approve assuming you have a good answer.

[michaelfig]

I love it! This is totally clear and maintainable.

[michaelfig]

Since I don't really know the motivation behind having a separate 'test' bootstrap version (I think just that it was different than the 'main' mode for vaults), is there a reason its result should be ignored? Is this just codifying behaviour we already had, avoiding a flake, or something else?