cron-conda.yml has no dev-version gate; can publish a .devN build to Anaconda #2458

Summary

#2452 adds a PCAPKIT_DEV_RELEASE gate to create-release.yml's four publish jobs so a .devN version on main never gets tagged/released. .github/workflows/cron-conda.yml is a separate workflow with the same publish capability and no equivalent gate.

Detail

conda-tag and conda-dist in cron-conda.yml publish __version__ to Anaconda (under the dev label) whenever publishes == 'true' and CONDA_CHANGED == 'true', independent of whether the version is a .devN release. If the intent behind #2452 is that a dev-in-progress version should never publish anywhere, this is the same gap in a different workflow.

Proposed fix

Add the same is_devrelease check (or reuse the computed PCAPKIT_DEV_RELEASE output if it can be shared/recomputed cheaply) as a condition on conda-tag/conda-dist in cron-conda.yml.