Update to GCC 11

[bdice]

This PR updates builds to use GCC 11.

[bdice]

Please do not merge until all RAPIDS repos are ready to migrate. (I do not have privileges to add the DO NOT MERGE label to prohibit merging.)

[raydouglass]

/merge

[jakirkham]

Thanks Bradley and everyone for reviewing! 🙏

Noticed there are a couple spots where we have GCC 9 still. Should we update these too (cc @gigony who may have thoughts here)?

cucim/CONTRIBUTING.md

Line 86 in c16ec7e

* `gcc` version 9.0+

cucim/CONTRIBUTING.md

Line 108 in c16ec7e

## Local Development using Conda Environment (for gcc 9.x and nvcc 11.0.x)

cucim/dependencies.yaml

Line 61 in c16ec7e

- gcc_linux-aarch64=9.*

cucim/docker/Dockerfile-cmake

Lines 51 to 52 in c16ec7e

	gcc-9 \
	g++-9 \

cucim/docker/Dockerfile-cmake

Lines 68 to 72 in c16ec7e

	# Setup gcc-9
	RUN update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-7 10 \
	&& update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-9 20 \
	&& update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-7 10 \
	&& update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-9 20

cucim/cpp/plugins/cucim.kit.cumed/cmake/deps/cli11.cmake

Lines 38 to 41 in c16ec7e

	# Note that library had a failure with nvcc compiler and gcc 9.x headers
	# ...c++/9/tuple(553): error: pack "_UElements" does not have the same number of elements as "_Elements"
	# __and_<is_nothrow_assignable<_Elements&, _UElements>...>::value;
	# Not using nvcc for main code that uses cli11 solved the issue.

[bdice]

I’ll fix dependencies.yaml.

I didn’t want to touch the Dockerfiles without discussing (and forgot to mention it here, sorry). I wasn’t sure how those are used or tested.

As for the contributing guide, the package should still build with GCC 9 for now, so I leave it to your discretion on whether we update the minimum required version.

[gigony]

Thanks Bradley and everyone for reviewing! pray

Noticed there are a couple spots where we have GCC 9 still. Should we update these too (cc @gigony who may have thoughts here)?

cucim/CONTRIBUTING.md

Line 86 in c16ec7e

* `gcc` version 9.0+

cucim/CONTRIBUTING.md

Line 108 in c16ec7e

## Local Development using Conda Environment (for gcc 9.x and nvcc 11.0.x)

cucim/dependencies.yaml

Line 61 in c16ec7e

- gcc_linux-aarch64=9.*

cucim/docker/Dockerfile-cmake

Lines 51 to 52 in c16ec7e

	gcc-9 \
	g++-9 \

cucim/docker/Dockerfile-cmake

Lines 68 to 72 in c16ec7e

	# Setup gcc-9
	RUN update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-7 10 \
	&& update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-9 20 \
	&& update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-7 10 \
	&& update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-9 20

cucim/cpp/plugins/cucim.kit.cumed/cmake/deps/cli11.cmake

Lines 38 to 41 in c16ec7e

	# Note that library had a failure with nvcc compiler and gcc 9.x headers
	# ...c++/9/tuple(553): error: pack "_UElements" does not have the same number of elements as "_Elements"
	# __and_<is_nothrow_assignable<_Elements&, _UElements>...>::value;
	# Not using nvcc for main code that uses cli11 solved the issue.

As @bdice mentioned, I think updating dependencies.yaml would be enough for now.

cucim/docker/Dockerfile-cmake is not used by RAPIDS CI/CD so it's okay to leave as it is.

This file(
cucim/cpp/plugins/cucim.kit.cumed/cmake/deps/cli11.cmake) is also okay to leave as it is.