🧪 Sync reusable-cibuildwheel.yml w/ upstream

[webknjaz]

What do these changes do?

This is an infra change that generalizes the cibuildwheel workflow as a part of preparation to my effort of further extraction externally.

This includes having input names in line with reusable-tox.yml and configuring cibuildwheel via env vars passed through inputs.

Are there changes in behavior for the user?

Nope.

Related issue number

N/A

Checklist

• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes

[codspeed-hq]

CodSpeed Performance Report

Merging #1193 will degrade performances by 26.04%

_{Comparing webknjaz:maintenance/generic-gha-cibuildwheel (0072f7e) with master (5ab49a5)}

Summary

❌ 3 regressions
✅ 241 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	BASE	HEAD	Change
❌	test_cimultidict_getall_istr_miss[py]	177.6 µs	236.4 µs	-24.85%
❌	test_multidict_getall_str_hit[cs-py]	1.8 ms	2.2 ms	-17.22%
❌	test_multidict_getall_str_miss[ci-py]	174 µs	235.3 µs	-26.04%

[asvetlov]

@webknjaz could you wait for tomorrow please.
The PR looks promising but I'm too tired now, I'd like to carefully review next day.

[webknjaz]

I don't need a review, really. It's thing I'll be hosting outside aio-libs, eventually. This is to ease the migration.

[asvetlov]

I don't need a review, really. It's thing I'll be hosting outside aio-libs, eventually.

It scares me a little. Is there any chance of having write access to these outside things for aio-libs admins?
In case something breaks in the future?

[webknjaz]

It's going to be PyPA so no. But I'm not migrating just yet. I need to solve a few things and document usage strategies.