update bioconductor-rhdf5: rebuild after including libcurl dependency downstream in bioconductor-rhdf5lib, include pin_subpackage syntax

[dlaehnemann]

I think that this will fix an issue with libcrypto.so not being found that I reported over at rhdf5: grimbough/rhdf5#131

Describe your pull request here

---

Please read the guidelines for Bioconda recipes before opening a pull request (PR).

General instructions

• If this PR adds or updates a recipe, use "Add" or "Update" appropriately as the first word in its title.
• New recipes not directly relevant to the biological sciences need to be submitted to the conda-forge channel instead of Bioconda.
• PRs require reviews prior to being merged. Once your PR is passing tests and ready to be merged, please issue the @BiocondaBot please add label command.
• Please post questions on Gitter or ping @bioconda/core in a comment.

Instructions for avoiding API, ABI, and CLI breakage issues

Conda is able to record and lock (a.k.a. pin) dependency versions used at build time of other recipes.
This way, one can avoid that expectations of a downstream recipe with regards to API, ABI, or CLI are violated by later changes in the recipe.
If not already present in the meta.yaml, make sure to specify run_exports (see here for the rationale and comprehensive explanation).
Add a run_exports section like this:

build:
  run_exports:
    - ...

with ... being one of:

Case	run_exports statement
semantic versioning	{{ pin_subpackage("myrecipe", max_pin="x") }}
semantic versioning (0.x.x)	{{ pin_subpackage("myrecipe", max_pin="x.x") }}
known breakage in minor versions	{{ pin_subpackage("myrecipe", max_pin="x.x") }} (in such a case, please add a note that shortly mentions your evidence for that)
known breakage in patch versions	{{ pin_subpackage("myrecipe", max_pin="x.x.x") }} (in such a case, please add a note that shortly mentions your evidence for that)
calendar versioning	{{ pin_subpackage("myrecipe", max_pin=None) }}

while replacing "myrecipe" with either name if a name|lower variable is defined in your recipe or with the lowercase name of the package in quotes.

Bot commands for PR management

Please use the following BiocondaBot commands:

Everyone has access to the following BiocondaBot commands, which can be given in a comment:

@BiocondaBot please update	Merge the master branch into a PR.
@BiocondaBot please add label	Add the please review & merge label.
@BiocondaBot please fetch artifacts	Post links to CI-built packages/containers. You can use this to test packages locally.

Note that the @BiocondaBot please merge command is now depreciated. Please just squash and merge instead.

Also, the bot watches for comments from non-members that include @bioconda/<team> and will automatically re-post them to notify the addressed <team>.

[dlaehnemann]

It seems like I missed a number of previous PRs that relate to the same issue. At the time, this was fixed by adding an openssl dependency:

• This PR introduced the openssl dependency: bioconductor-rhdf5: add openssl lib to reqs #31063
• This issue reports that this didn't actually fix the problem: bioconductor-hdf5 incompatibility with other packages due to new openssl 3 #31072
• This PR further cleaned this up: Fix openssl dep for bioc-rhdf5 and bioc-hdf5array #31189

But then, for some reason this was lost again in this bulk PR:
#42063

[dlaehnemann]

The libcurl dependency actually belongs downstream in bioconductor-rhdf5lib.

This is the PR that handles this:
#43930

And here's the discussion that pinpoints where the libcurl dependency belongs:
grimbough/rhdf5#131 (comment)

But I'll use this PR to include the pin_subpackage syntax and get a rebuild of the package.

[dlaehnemann]

This is now rebuilt with the latest bioconductor-rhdf5filters and thus the latest bioconductor-rhdf5lib. So this should be fine to merge, if anybody wants to give a quick review.