Move interactive functions to cmd

[phillebaba]

Describe what should be investigated or refactored

We have a lot of code that uses interactive functions to get user input in our library functions. This requires the code to be aware of it is being used in a context where user input could be fetched. Making the code questionably thread safe in these situations if it were to be called in parallel.

It would be best to move any use of code related to user input to the cmd package. In the future any code that is being exported for library use should not concert itself with user input.

Links to any relevant code

zarf/src/pkg/packager/creator/template.go

Lines 35 to 37 in 8100c69

	setVal, err := interactive.PromptVariable(v1alpha1.InteractiveVariable{
	Variable: v1alpha1.Variable{Name: key},
	})

zarf/src/pkg/packager/filters/deploy.go

Lines 138 to 141 in 8100c69

	component, err := interactive.SelectChoiceGroup(group)
	if err != nil {
	return nil, fmt.Errorf("%w: %w", ErrSelectionCanceled, err)
	}

zarf/src/pkg/packager/filters/deploy.go

Lines 170 to 173 in 8100c69

	selected, err := interactive.SelectOptionalComponent(component)
	if err != nil {
	return nil, fmt.Errorf("%w: %w", ErrSelectionCanceled, err)
	}

Additional context

N/A

[brandtkeller]

Should be considered in context for #3525