cidata: identify vmtype-specific boot scripts

[AkihiroSuda]

https://github.com/lima-vm/lima/tree/master/pkg/cidata/cidata.TEMPLATE.d/boot

VMtype-specific boot scripts (02-wsl2-setup.sh, 05-rosetta-volume.sh, and others?) should be consolidated to the same step.

These scripts should be eventually decoupled from the core of Lima, and should be provided by VM drivers

[afbjorklund]

I think the wsl2-setup / lima-init can be decoupled separately, and does not have to be provided by the VM drivers.

Otherwise, it will duplicated in each driver: WSL2, Apple Containers, Kata Containers - everything without cloud-init

But it does need a different feature check (than checking vmType):

• Remove VMType check from the lima-init boot script #3861

pkg/cidata/cidata.go:   if args.VMType == limayaml.WSL2 {

pkg/cidata/cidata.TEMPLATE.d/boot/02-wsl2-setup.sh:[ "$LIMA_CIDATA_VMTYPE" = "wsl2" ] || exit 0

[jandubois]

Maybe drivers need a mechanism to specify/override LIMA_CIDATA_* variables, so they can configure builtin boot scripts (maybe @unsuman has implemented this; I haven't checked the code).

[unsuman]

No, actually, I have only implemented a function in the driver package(BootScripts()) and moved the driver-specific boot scripts under driver/boot(only vz for now).
See this. Do you think the approach is any good?

LIMA_CIDATA_* variables

Can you please elaborate and set some context on what it does so that I can try to add it to the recent PR?