Use new buildkite pipeline names

[def-]

See #26502 for context

Checklist

• This PR has adequate test coverage / QA involvement has been duly considered.
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
• This PR includes the following user-facing behavior changes:

[def-]

I just noticed this can't work yet since Github still waits for buildkite/tests instead of buildkite/test. I'll try to find where that is configured, but probably I can't change it.

[def-]

@benesch I guess you will have permissions to change that in https://github.com/MaterializeInc/materialize/settings (from buildkite/tests to buildkite/test) I renamed the Test pipeline back to Tests for now: https://buildkite.com/materialize/tests/settings/repository

[benesch]

Yes, I can work on this as soon as I have a free second at my computer.

…

On Tue, Apr 9, 2024 at 5:41 AM Dennis Felsing ***@***.***> wrote: @benesch <https://github.com/benesch> I guess you will have permissions to change that in https://github.com/MaterializeInc/materialize/settings (from buildkite/tests to buildkite/test) I renamed the Test pipeline back to Tests for now: https://buildkite.com/materialize/tests/settings/repository — Reply to this email directly, view it on GitHub <#26517 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGXSIBXT56NW5TXRC7E563Y4OZVPAVCNFSM6AAAAABF6F3Q4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBUGU4DGMBWGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[nrainer-materialize]

@def-: Rebased for your convenience to resolve conflicts introduced with the merge of #26497.