chore: add vagrant configuration with complete dev environment

[jmickey]

What this PR does / why we need it:

PR adds a few things.

1. Vagrantfile with fully scripted development environment setup
2. Basic containerd configuration
3. Adds .vagrant folder to gitignore

Release note:

Add Vagrantfile with Ubuntu Focal for dev environment

[codecov-commenter]

Codecov Report

Merging #123 (e73148e) into main (ca14a16) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #123   +/-   ##
=======================================
  Coverage   40.09%   40.09%           
=======================================
  Files          32       32           
  Lines        1444     1444           
=======================================
  Hits          579      579           
  Misses        789      789           
  Partials       76       76           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7b5ff28...e73148e. Read the comment docs.

[yitsushi]

lgtm

Manual testing

1. The selected box does not support libvirt

	config.vm.provider :libvirt do |libvirt|
		libvirt.connect_via_ssh = false
		libvirt.username = "root"
		libvirt.storage_pool_name = "vagrant"
	end

2. Installed vbox
3. Tried to do with vbox (vagrant up --provider=virtualbox)
4. The virtual machine did not boot (vagrant timeout)
   checked with the vbox gui, something: invalid settings for graphics controller
5. I assume it's working on mac ;)

[yitsushi]

This one might be low later on, it's good now, but when we are creating 3 MicroVMs and configuring ak8s cluster on them, that 2 vpcu will be low and I think memory too.

Now it's fine, we can update later, just wanted mention it.

[yitsushi]

Updated the PR description with Release note to satisfy Release notes check.

Somehow the checker still does not see the code-block:

action failed: executing action function: no release-note code block found

@jmickey: can you try to force-push to the branch, maybe it can invalidate the cache. I assume it's cached and that's why it cries.

[jmickey]

@yitsushi I added a libvirt provider. Feel free to give it a shot. The releasenote check is passing now.

[yitsushi]

@jmickey : I tried with my own snippet above, but the issue is the selected box does not support libvirt

config.vm.box = "ubuntu/focal64"

and I don't think there is a real value to add it and later hear "it's in there, but does not work, fix it"

The box you're attempting to add doesn't support the provider
you requested. Please find an alternate box or use an alternate
provider. Double-check your requested provider to verify you didn't
simply misspell it.

If you're adding a box from HashiCorp's Vagrant Cloud, make sure the box is
released.

Name: ubuntu/focal64
Address: https://vagrantcloud.com/ubuntu/focal64
Requested provider: [:libvirt]

[jmickey]

Ah right you are. I can switch it to generic/ubuntu2004

[jmickey]

@yitsushi Switched to a ubuntu box that has libvirt compatibility, should be good now.

[yitsushi]

Manual test

1. Changed storage pool name, because I use kvm for other things too, and with default it has conflicts, but that does not matter
2. vagrant up
3. Everything is working

Added commit: see commit message