Related work items: microsoft#1067, microsoft#1097, microsoft#1119, microsoft#1170, microsoft#1176, microsoft#1180, microsoft#1181, microsoft#1182, microsoft#1183, microsoft#1184, microsoft#1185, microsoft#1186, microsoft#1187, microsoft#1188, microsoft#1189, microsoft#1191, microsoft#1193, microsoft#1194, microsoft#1195, microsoft#1196, microsoft#1197, microsoft#1200, microsoft#1201, microsoft#1202, microsoft#1203, microsoft#1204, microsoft#1205, microsoft#1206, microsoft#1207, microsoft#1209, microsoft#1210, microsoft#1211, microsoft#1218, microsoft#1219, microsoft#1220, microsoft#1223

…te kernel and userland (initrd.img) (microsoft#1206)

Mainly this refactors the code that creates the hcs api json document into two paths. One is the previous
logic that will create a kernel command line and boot the kernel and userland from individual files using
the "LinuxKernelDirect" scheme. With isolation enabled this must be replaced with "GuestState/GuestStateFilePath"
etc to load from a vmgs file.

There are updates and addition files in the schema2 directory to support the newer hcs API so that the existing
way where an object that represents the hcs api json is built and then serialised to json can be used with
isolation_setting etc.

If a SecurityPolicy annotation is present it will boot the vmgs file unless
"io.microsoft.virtualmachine.lcow.no_security_hardware" is set to true. The various example pod.json files
will need to be updated for use with non SNP machines.

Signed-off-by: Ken Gordon <[email protected]>