Submit openmassspec-io + openmassspec to conda-forge

[Nathan-D-R]

RELEASING.md documents a two-stage conda-forge submission
(openmassspec-io first via staged-recipes, then the openmassspec
metapackage whose run requirement includes it), but it was never done.
Now that 1.1.0 is stable on crates.io + PyPI with all five vendors, a
conda-forge feedstock would reach the large share of MS/bioinformatics
users who live in conda environments.

Scope: follow the SOP in RELEASING.md - build each recipe locally in
condaforge/linux-anvil-cos7-x86_64 against conda-forge-pinning before
opening the PR, declare {{ stdlib("c") }} for the compiled binding, and
submit openmassspec-io first, then openmassspec once the feedstock
lands.

[Nathan-D-R]

Update, 2026-07-18: this is now more stale than when filed. The staged-recipes PR (conda-forge/staged-recipes#34167) that exists for openmassspec-io is still pinned to 1.1.0 - we're now at 1.5.0, which also added a sixth vendor (Shimadzu, openszraw) that PR doesn't know about at all. Two things to reconcile when this gets picked up:

• Whether to update #34167 in place to target 1.5.0 (with Shimadzu wired in via the shimadzu feature/openszraw dep), or let it land as 1.1.0 first and follow up separately - probably the former, same as how the stale pre-rename openproteo-io PR (#34069) was handled: closed and replaced rather than patched, per [[project_conda_forge_staged_recipes]].
• The openmassspec metapackage recipe still can't be submitted until the openmassspec-io feedstock actually exists (its run: dependency needs the feedstock for the solver) - unchanged from the original scope note.