Distinguish between pyodide-build and pypa/build as build frontends when handling build verbosity

[agriyakhetarpal]

See #2605

cc: @AndrewAnnex

[agriyakhetarpal]

I don't think this is the right approach at the moment, and I should try another way. What I think happens here is that _get_verbosity_flags will get wrapped in get_build_frontend_extra_flags, which will be called at the time of Pyodide builds. However, the finalisation of the build frontend flags happens outside and before the pyodide build command is called, which means the PYODIDE environment variable is set during the wheel builds and not when cibuildwheel performs its own preparation for the build, which means that this will fail to remove the verbosity-related flags.

[henryiii]

What's the status here?

[joerick]

I thought myself and Agriya talked about this but I can't see the convo. As I remember, the environment variable approach won't work due to when/where it's set and read. My feeling is that we should actually split out pyodide build as a separate build frontend option from build, as they actually do have different command line frontends. Once we've done that, this kind of change becomes easy too.