Merge vagrant_40_gb_bionic into ubuntu/bionic [a=patviafore] [r=rcj]

Make Ubuntu Vagrant box 40G. (LP: #1580596)

Vagrant images were previously put at 10G, but this was a regression
from Trusty, in which they were 40G. This made it a tough sell for
users to upgrade if they were using a Ubuntu desktop experience.

This change does not impact disk usage as Vagrant with the virtualbox
provider dynamically allocates space with the VMDK. On a test system,
the VMDK took up 1.1G of disk space according to df, and after
creating a 2G file in Vagrant, the VMDK grew to 3.1G.

Therefore, users who are running on a system with little free space will
not see adverse effects if they upgrade to a new vagrant image

MP: https://code.launchpad.net/~patviafore/livecd-rootfs/+git/livecd-rootfs/+merge/384635

debian/changelog

@@ -1,3 +1,9 @@
+livecd-rootfs (2.525.48) UNRELEASED; urgency=medium
+
+  * Increase Vagrant disk size from 10G to 40G (LP: #1580596) 
+
+ -- Patrick Viafore <patrick.viafore@canonical.com>  Fri, 22 May 2020 15:16:16 -0500
+
 livecd-rootfs (2.525.47) bionic; urgency=medium
 
   * Apparently the lxd appliance needs to use a custom track (4.0) and since

live-build/ubuntu-cpc/hooks.d/base/vagrant.binary

@@ -97,7 +97,7 @@ distro=$(chroot chroot lsb_release --id --short | tr [:upper:] [:lower:])
 # Get the VMDK in place
 prefix="${distro}-${suite}-${version}-cloudimg"
 vmdk_f="${box_d}/${prefix}.vmdk"
-create_vmdk ${derivative_img} ${vmdk_f}
+create_vmdk ${derivative_img} ${vmdk_f} 40960
 
 ####################################
 # Create the ConfigDrive