Make sure that ansible params check the playbook

[afbjorklund]

The ansible provisioning supports using a separate yaml playbook,
so check this file (but only the top playbook) for any parameters...

The ansible-playbook command does not run remotely so it does not
use the param.env, which means that the env is set on the command.

[afbjorklund]

The ansible provisioning was missed in the original "params" feature addition:

• Add limayaml param settings to provisioning script environment #2570

A similar change to the verification would need be needed for any external scripts:

• Allow providing scripts as separate files #2442

i.e. to check any "path", in addition to "script"

again, checking only the top path should be OK

[jandubois]

This PR seems to be missing a check in

lima/hack/test-templates.sh

Lines 158 to 163 in 16fd466

	INFO 'Testing that PARAM env variables are exported to all types of provisioning scripts and probes'
	limactl shell "$NAME" test -e /tmp/param-boot
	limactl shell "$NAME" test -e /tmp/param-dependency
	limactl shell "$NAME" test -e /tmp/param-probe
	limactl shell "$NAME" test -e /tmp/param-system
	limactl shell "$NAME" test -e /tmp/param-user

limactl shell "$NAME" test -e /tmp/param-ansible

[jandubois]

similar change to the verification would need be needed for any external scripts:

• Allow providing scripts as separate files #2442

i.e. to check any "path", in addition to "script"

again, checking only the top path should be OK

I don't understand what this means.

[afbjorklund]

For the "script", we check the parameter - for the "path", it needs an os.ReadFile first

[afbjorklund]

This PR seems to be missing a check

I renamed the file, to look like the others.

[alexandear]

Can be simplified:

Suggested change

	env := []string{}
	env = append(env, os.Environ()...)
	env := os.Environ()