Add jaeger-client-cpp v0.9.0

[amitsingh21]

Summary

Add jaeger-client-cpp — C++ client for Jaeger distributed tracing.

• Implements OpenTracing API
• Apache-2.0 license
• Includes patchelf --add-needed libthrift.so fix: the linker's --as-needed strips thrift from NEEDED because jaeger uses it only via RTTI/vtables, causing runtime symbol lookup failures
• Depends on opentracing-cpp (submitted in separate PR)
• Note: project is deprecated in favor of OpenTelemetry, but still widely used

Checklist

• License file included
• Recipe uses recipe.yaml (v1 format)
• Tests check for header and library
• Build works on linux-64
• Depends on opentracing-cpp which is also being submitted (Add opentracing-cpp v1.6.0 #32900)

🤖 Generated with Claude Code

[conda-forge-admin]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipes/jaeger-client-cpp/recipe.yaml) and found some lint.

Here's what I've got...

For recipes/jaeger-client-cpp/recipe.yaml:

• ❌ The recipe could do with some maintainers listed in the extra/recipe-maintainers section.
• ❌ This recipe is using a compiler, which now requires adding a build dependence on ${{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler.

For recipes/jaeger-client-cpp/recipe.yaml:

• ℹ️ You should not need to depend on libboost directly. If your package is linking to boost libraries, use libboost-devel in the host environment (which will create the correct dependence at runtime through a run-export), or use libboost-headers if you only need the boost headers.

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

[github-actions]

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

[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 (recipes/jaeger-client-cpp/recipe.yaml) and found it was in an excellent condition.

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

For recipes/jaeger-client-cpp/recipe.yaml:

• ℹ️ You should not need to depend on libboost directly. If your package is linking to boost libraries, use libboost-devel in the host environment (which will create the correct dependence at runtime through a run-export), or use libboost-headers if you only need the boost headers.

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

[conda-forge-admin]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipes/jaeger-client-cpp/recipe.yaml) and found some lint.

Here's what I've got...

For recipes/jaeger-client-cpp/recipe.yaml:

• ❌ In conda-forge.yml: $ = {'skip_render': ['.github/workflows'], 'win': {'enabled': False}}.

  Additional properties are not allowed ('win' was unexpected)

  Schema

For recipes/jaeger-client-cpp/recipe.yaml:

• ℹ️ You should not need to depend on libboost directly. If your package is linking to boost libraries, use libboost-devel in the host environment (which will create the correct dependence at runtime through a run-export), or use libboost-headers if you only need the boost headers.

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

[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 (recipes/jaeger-client-cpp/recipe.yaml) and found it was in an excellent condition.

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

For recipes/jaeger-client-cpp/recipe.yaml:

• ℹ️ You should not need to depend on libboost directly. If your package is linking to boost libraries, use libboost-devel in the host environment (which will create the correct dependence at runtime through a run-export), or use libboost-headers if you only need the boost headers.

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