Avoid undefined jinja errors for skipped recipes

[msarahan]

Description

A few NVIDIA feedstocks on conda-forge have been failing to re-render lately. See conda-forge/cuda-nvdisasm-feedstock#12. The expected behavior was that undefined jinja variables shouldn't error out when the metadata is skipped.

I tracked it back to #5371, which I think is a good code improvement. In order to avoid these irrelevant errors for skipped recipes, we just abort after the first parsing pass.

Checklist - did you ...

• Add a file to the news directory (using the template) for the next release's release notes?
• Add / update necessary tests?
• Add / update outdated documentation?

[codspeed-hq]

CodSpeed Performance Report

Merging #5458 will not alter performance

_{Comparing msarahan:exit-render-early-on-skip (b8367cf) with main (f702c3a)}

Summary

✅ 3 untouched benchmarks

[jakirkham]

Thanks Michael! 🙏

If it is helpful, here is a generic example ( conda-forge/conda-smithy#2011 )

[jakirkham]

Thanks Michael! 🙏

Looks like this is passes

Canary builds fail, but those are pointing out deprecations in other tests. Think we can safely ignore those here

[jakirkham]

@kenodegard could you please take a look as well? 🙂

[kenodegard]

The tests are blocked by conda/conda#14169

[jakirkham]

Thanks Bianca and Ken! 🙏

[kenodegard]

macOS tests are failing due to #5470

[msarahan]

Thanks for sticking with this through the slog, @beeankha and @kenodegard