[Packaging] Add Debian 11 Bullseye support

[jiasli]

Description

Fix #19326, #18654, and possibly #18895, #18804, #18798, #16783

Debian releases and their life cycle can be found at

• https://www.debian.org/releases/
• https://wiki.debian.org/DebianReleases

Similar to #19367, we need to support Debian 11 Bullseye, otherwise the buggy unofficial Azure CLI from https://packages.debian.org/bullseye/azure-cli will be installed.

[jiasli]

debian:bullseye has libssl1.1 installed by default.

$ docker run --rm debian:bullseye /usr/bin/apt list --installed | grep libssl

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libssl1.1/now 1.1.1k-1 amd64 [installed,local]

So no need to add bullseye to

azure-cli/scripts/release/debian/test_deb_in_docker.sh

Lines 12 to 13 in ba4cd3b

	case ${DISTRO} in
	bionic|buster|focal|groovy) apt install -y libssl1.1;;

[jiasli]

As Python's docker image is now based on Bullseye (docker-library/python#633), this makes Bullseye support more necessary.

[Chuxel]

@jiasli In addition, the debian, golang, ruby, php, buildpack-deps and more images have moved. There's great interest in agressivley moving to bullseye due to a segfault in Debian 10/buster on M1 macs.

While a workaround script could unblock, the Docker ecosystem moves quickly and doing so feels pretty iffy TBH.

[jiasli]

We only release packages for AMD64. The bundled Python is for AMD64.

M1 is not one of the supported architecture, including ARM64. It is very likely even if we release a package for bullseye, running the packaging on M1 Macs will fail. In such case, pip install is the only solution.

[jiasli]

Debian 11 Bullseye support will be release in Azure CLI 2.28.0 on 09/07/2021.

[jiasli]

Debian 11 Bullseye package has been released:

• https://packages.microsoft.com/repos/azure-cli/dists/bullseye/
• https://packages.microsoft.com/repos/azure-cli/pool/main/a/azure-cli/azure-cli_2.28.0-1~bullseye_all.deb