feat!: filter package components with strategy interface

[Noxsios]

Description

Consolidate component filtering logic into a filters package. Each filter is an implementation of

// ComponentFilterStrategy is a strategy interface for filtering components.
type ComponentFilterStrategy interface {
	Apply(types.ZarfPackage) ([]types.ZarfComponent, error)
}

Public construction functions return instances of this interface not instances of their underlying structs. Consumers should be fully cognizant of which filter they are using, and should not be making a common wrapper function (eg. NewFilter(args...) to dynamically return a filter.

ex:

func Empty() ComponentFilterStrategy {
	return &emptyFilter{}
}

// emptyFilter is a filter that does nothing.
type emptyFilter struct{}

// Apply returns the components unchanged.
func (f *emptyFilter) Apply(pkg types.ZarfPackage) ([]types.ZarfComponent, error) {
	return pkg.Components, nil
}

BREAKING CHANGES: This changes the interface signatures on sources.PackageSource to reflect the new behavior whereupon the zarf.yaml is loaded into memory within the sources load operations. This allows for filtering to take place during load and for the zarf.yaml in memory to reflect these filter operations.

Related Issue

Fixes #2320

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Other (security config, docs update, etc)

Checklist before merging

• Test, docs, adr added or updated as needed
• Contributor Guide Steps followed

[netlify]

✅ Deploy Preview for zarf-docs canceled.

Name	Link
🔨 Latest commit	eed0129
🔍 Latest deploy log	https://app.netlify.com/sites/zarf-docs/deploys/65fb699ce378b700080003cf

[lucasrod16]

I don't have a strong opinion on whether filter implementations return the strategy interface or the implementation struct.

My preference would be to return the concrete implementation struct because it makes the code a bit easier to navigate imo. For example, when I click into Apply() in vs code in the client code, it takes me to the interface method signature instead of the implementation. It would be nice to be taken directly to the implementation, but not a big enough reason to outweigh other factors.

[AustinAbro321]

A few small things mostly questions on my end

[AustinAbro321]

LGTM