testplans: release.json - Add 2 new manual tests

Add a couple new tests to release.json:

1) Test that avocado-virt can assign values to the
   command line correctly.
2) Run the avocado migration test, as it's a fairly
   complex test that exercises a lot of functionality
   in avocado-virt.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

examples/testplans/release.json

@@ -45,6 +45,12 @@
 	{"name": "Avocado Virt Boot Test Run and HTML report",
 	 "description": "Now that your system is setup to run virtualization tests, run the boot test with `$ avocado run avocado-virt-tests/qemu/boot.py --sysinfo on --open-browser`. Expected result: `PASS`, followed by a web browser showing an HTML report"},
 
+	{"name": "Avocado Virt - Assignment of values from the cmdline",
+	 "description": "Test that we can assign values from the cmdline. Create a new qemu bin path, for example sudo ln -s `/usr/bin/qemu-kvm /usr/bin/qemu-kvm-avocado-functional`, then run the boot test with `$ avocado run avocado-virt-tests/qemu/boot.py --qemu-bin /usr/bin/qemu-kvm-avocado-functional --sysinfo on --open-browser`. Expected result: `PASS`, followed by the web report. Look at the job log, it should list the path `/usr/bin/qemu-kvm-avocado-functional` in the QEMU command line."},
+
+	{"name": "Avocado Virt - Migration test",
+	 "description": "Run the boot test with `$ avocado run avocado-virt-tests/qemu/migration/migration.py --sysinfo on --open-browser`. Expected result: `PASS`, followed by a web browser showing an HTML report"},
+
 	{"name": "Avocado HTML report sysinfo",
 	 "description": "On the HTML report, click on `Sysinfo (pre job, click to expand)` and verify that system information such as `hostname` and `cpuinfo` are present and accurate"},