Migrate to GCC 11

[jdblischak]

conda-forge updated its GCC pinning from 10 to 11 2 weeks ago (conda-forge/conda-forge-pinning-feedstock#3731). This migration has been well tolerated by TileDB-VCF (source) and TileDB-R (source)

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• 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.

[conda-forge-linter]

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.

[akrherz]

Thank you. My own curiosity gets the best of me... What is driving this PR? Is there not a migrator coming or ?

[jdblischak]

The main motivation is that this change is automatically made any time we rerender any of the other tiledb-related feedstocks. @ihnorton had me roll back the GCC migration in PR TileDB-Inc/tiledb-vcf-feedstock#60 (review) because he was worried about compatibility issues throughout the tiledb stack. But this change has already been merged to TileDB-VCF and TileDB-R seemingly without consequence, so I figured we should explicitly make the change here as well.

To summarize, as we migrate the TileDB clients to libtiledb 2.13, the conda-forge machinery is automatically bumping the GCC version. Thus I wanted to migrate the core library too. Otherwise it likely wouldn't happen until the next TileDB release

There's no rush, so we can wait until @ihnorton or @Shelnutt2 approves