Init fails if $HOME is not defined

[Noxsios]

Environment

Device and OS: Intel NUC on Ubuntu 22.04
App version: v0.42.0
Kubernetes distro being used: RKE2
Other: Running init as systemd service

Steps to reproduce

1. Run zarf init as a user / profile w/ no $HOME env variable.
2. Init fails due to always attempting to find user's homedir during file copying.

zarf/src/pkg/packager/deploy.go

Line 426 in 09c41a1

target, err := config.GetAbsHomePath(strings.Replace(file.Target, "###ZARF_TEMP###", p.layout.Base, 1))

GetAbsHomePath needs a slight changeup in logic, it should only try to calculate homePath if ~ is found in the string, otherwise no home path expansion is needed.

zarf/src/config/config.go

Lines 105 to 115 in 09c41a1

	func GetAbsHomePath(path string) (string, error) {
	homePath, err := os.UserHomeDir()
	if err != nil {
	return "", err
	}
	if strings.HasPrefix(path, "~") {
	return strings.Replace(path, "~", homePath, 1), nil
	}
	return path, nil
	}

Visual Proof (screenshots, videos, text, etc)

ERROR:  failed to deploy bundle: unable to deploy component "zarf-injector": unable to process the component files: $HOME is not defined

Severity/Priority

Low, can define a dummy $HOME in the meantime.

[phillebaba]

While I may agree that we could flip the order of the logic here, I do wonder why the system is not setting the home environment variable?