(RE-13304) add apt-transport-https to debian

[mihaibuzgau]

the puppet-release package is now setting the url for apt puppet-agent repo to https transport. On the default Debian installation < 10 apt-transport-https is not provided causing the installation of puppet-agent to fail.
This PR adds apt-transport-https to the provisioning phase of beaker.

[mihaibuzgau]

beaker provision on debian-8:

[redacted] (debian8-64-1) 11:28:20$ dpkg -s apt-transport-https
  Package: apt-transport-https
  Status: install ok installed
  Priority: optional
  Section: admin
  Installed-Size: 190

Debian 9:

[redacted](debian9-64-1) 11:36:31$ apt-get install --force-yes  -y apt-transport-https
  Reading package lists...
  Building dependency tree...
  Reading state information...
  The following NEW packages will be installed:
    apt-transport-https
  0 upgraded, 1 newly installed, 0 to remove and 176 not upgraded.
  Need to get 171 kB of archives.

Debian 10:

[redacted] (debian10-64-1) 11:42:08$ apt-get install --force-yes  -y apt-transport-https
  Reading package lists...
  Building dependency tree...
  Reading state information...
  The following NEW packages will be installed:
    apt-transport-https
  0 upgraded, 1 newly installed, 0 to remove and 84 not upgraded.

Ubuntu 14.04 - already installed

root@[redacted]:~# apt list --installed | grep apt-transport-https

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

apt-transport-https/now 1.0.1ubuntu2.6 amd64 [installed,upgradable to: 1.0.1ubuntu2.18]

Ubuntu 16.04 - already installed

root@[redacted]:~# apt list --installed | grep apt-transport-https

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

apt-transport-https/xenial-updates,now 1.2.27 amd64 [installed]

Ubuntu 18.04 - not installed and not needed, since it knows how to handle https repos.

[Magisus]

This is blocking puppetserver's pipelines too, when installing PuppetDB, from this function https://github.com/puppetlabs/beaker-puppet/blob/master/lib/beaker-puppet/install_utils/foss_utils.rb#L1062-L1064. However, I wasn't seeing the problem go away there when I added the contents of this PR to my local beaker. Does this only come into effect when using the provision subcommand? Our jobs currently don't, but we could probably update them to do so if needed.

[mihaibuzgau]

@Magisus that's correct, the packages will be installed by using beaker provision command.

[Magisus]

Thanks, I'll look into adding that for our jobs!

[Magisus]

Got our test run using beaker subcommands and confirmed this fixes our issue too.