tests/ci: Collect environment information

[bofh]

Summary

For reproducing errors or test results it is important to gather
environment information. These environments are divided into two parts.
One part is in which environment the artifacts were built into and the
second part is in which environment the tests were run.

This patch collects thesee information and saves into a .env file in
the metadir. After this patch lands we will also need to change our
jenkins job where we are uploading the artifact to a central location.
This environment file should also be stored along with the artifact.
For easier location the image basename and the environment basename are
kept same.

Test Plan

# make -C tests/ci ci-get-env gives a small glimpse of what are collected from the host system

After the end of make ci there will be an additional file ending with an extension .env which will also include the output of env from inside the vm.

[lwhsu]

There is no tar cvf ${tardev} -C ${metadir} . part in the "$freebsdci_type" = "smoke" path, will that be a problem?

[lwhsu]

In D54247#1239853, @lwhsu wrote:

There is no tar cvf ${tardev} -C ${metadir} . part in the "$freebsdci_type" = "smoke" path, will that be a problem?

Other than this I think this is fine. I would prefer separating the logic of handling meta file/device to other routines, but that can be done later.

[bofh]

In D54247#1239856, @lwhsu wrote:

In D54247#1239853, @lwhsu wrote:

There is no tar cvf ${tardev} -C ${metadir} . part in the "$freebsdci_type" = "smoke" path, will that be a problem?

Other than this I think this is fine. I would prefer separating the logic of handling meta file/device to other routines, but that can be done later.

To be frank I don't even see the point on getting the output of env for the smoke test as no applications are actually running. So I will most probably remove the set_environment routine from the "smoke" test.

[bofh]

Address the issue brought by @lshsu. Get env output in CI for smoke tests too.

[bofh]

In D54247#1239853, @lwhsu wrote:

There is no tar cvf ${tardev} -C ${metadir} . part in the "$freebsdci_type" = "smoke" path, will that be a problem?

For clarity and uniformity I have added it for both the cases.