[main] run test suite for libgrpc

[h-vetinari]

Rebase #311 onto main

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13587000216. Examine the logs at this URL for more detail.}

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint --conda-forge . from the recipe directory. You can also examine the workflow logs for more detail.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13597823650. Examine the logs at this URL for more detail.}

[h-vetinari]

Linter failure is unrelated

[h-vetinari]

Alright, with the unvendoring of upb around the corner in #394, I really want us to test that the resulting library is actually working. Upstream will rightly say that switching out upb "voids the warranty", but unfortunately we don't have a good alternative. Running the test suite at least gets us most of the way back to proving that the library is still ~fully functional. Windows unfortunately is both going to be too onerous for now to build (there are so many test configs in CMakeLists.txt that would constantly need patching), so let's just use unix on x64 as our canaries.