Bump h5py from 3.3.0 to 3.6.0

[dependabot]

Bumps h5py from 3.3.0 to 3.6.0.

Commits

• 3a4b4ee Merge pull request #2002 from takluyver/rever-3.6
• bea3fb4 Clean up extra whitespace
• 4fd1f6d Manually clean up release notes
• e359674 Updated CHANGELOG for 3.6.0
• 221bb01 bumped version to 3.6.0
• 9bbf39c Merge pull request #1987 from takluyver/ci-py-3.10-mac
• d4e4418 Merge pull request #2000 from takluyver/doc-rdcc-nslots-per-dataset
• 9933fa8 Merge pull request #1989 from takluyver/simplify-setitem-ext-link
• 699cfb0 Merge branch 'master' into ci-py-3.10-mac
• 078f416 Merge pull request #1999 from takluyver/test-mindeps-no-cython
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coveralls]

Pull Request Test Coverage Report for Build 1497240583

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 69.773%

---

Totals
Change from base Build 1497142667:	0.0%
Covered Lines:	11440
Relevant Lines:	16396

---

💛 - Coveralls

[niklassiemer]

Interestingly, mamba makes the difference here?!
The pip check fails with

  Found conflicts! Looking for incompatible packages.
  This can take several minutes.  Press CTRL-C to abort.
  failed
  Warning: 
  UnsatisfiableError: The following specifications were found to be incompatible with each other:

while using

    - uses: conda-incubator/setup-miniconda@v2
      with:
        auto-update-conda: true
        python-version: ${{ matrix.python-version }}
        channel-priority: strict
        environment-file: .ci_support/environment.yml

and all the unit tests run fine with

    - uses: conda-incubator/setup-miniconda@v2
      with:
        python-version: ${{ matrix.python-version }}
        mamba-version: "0.17.0"
        channels: conda-forge
        channel-priority: strict
        auto-update-conda: true  
        environment-file: .ci_support/environment.yml

Right now I do not understand why the environment can be solved with mamba but not with conda... I know both approaches may lead to different environments but if it is solvable, both should find one solution, shouldn't they?