Add libarrow-static package that contains static archives

[anubhavp28]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

Hi folks, what do you all think of having a libarrow-static package?

I use my conda environment to build python extensions, and having the static libraries of arrow, means we can reduce the run time dependencies of the extensions. This greatly reduce the number of times we have to rebuild it to work in different kinds of environments. We hide the symbols so, they don't leak and collide at runtime. Arrow is one of those packages which require a tight version pin at runtime.

[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:

• ℹ️ It looks like the 'libarrow-static' output doesn't have any tests.
• ℹ️ 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/37209938459. Examine the logs at this URL for more detail.}