Increased "Accountability" and python subset for CFEP03

### Comment:

I am hoping we can come to an agreement on how best to deal with CFEP03 additions and how to "retire them".

For example:
onnxruntime: https://github.com/conda-forge/onnxruntime-feedstock/pull/145

has been ready for 1 week, but it is unlikely that either @traversaro or I will be able to part with our windows workstations for long enough for these builds.

We are trying to use the external runners: https://github.com/conda-forge/onnxruntime-feedstock/pull/139
as well as condensing the builds https://github.com/conda-forge/onnxruntime-feedstock/pull/134 but ultimately these will take alot of work.

It would be good to establish rules on:
* Who is accountable for building the CFEP03 builds on various platforms, and in what acceptable timeframe.
* If we want to build a subset of the python matrix, should we try to coordinate accross conda-forge? I've been following:
* Even versions of python for my own internal projects. yearly python upgrades are too much churn for me.

Thoughts appreciated to help avoid delays in builds due to CFEP03.