feat: add use-all-catalogers flag

[cpendery]

Description

Add a new switch --use-all-catalogers that allows for the use of both image and file catalogers to run on the subject. This is useful when scanning an image built to use as a build environment, where artifacts may be installed using the files present soon.

Closes #1049

[cpendery]

While #1038 allows us to use the config to turn on certain catalogers, I think it would be easier for my use case, using all of them, to have a general switch to turn them all on. If there is an in between you all like, happy to adjust accordingly and contribute it.

[spiffcs]

Thanks for the PR here @cpendery!

Rather than make a new flag here I think we'd like to extend on the work done in #1038.

Notice how the config can now take a []string as Catalogers that syft should enable.

syft/internal/config/application.go

Line 50 in 546eaec

Catalogers []string `yaml:"catalogers" json:"catalogers" mapstructure:"catalogers"`

Test showing the catalogers option

syft/test/cli/packages_cmd_test.go

Lines 230 to 237 in 546eaec

	{
	name: "catalogers-option",
	args: []string{"packages", "-o", "json", "--catalogers", "python,ruby-gemspec", coverageImage},
	assertions: []traitAssertion{
	assertPackageCount(6),
	assertSuccessfulReturnCode,
	},
	},

If we use the flag --catalogers here and pass something like all we can keep the CLI surface area small while also extending the --catalogers flag ability to turn all options on with a single command.

Let me know what you think of this direction.

[spiffcs]

Added small comment about use of new flag vs extending a newly merged flag

[cpendery]

Added small comment about use of new flag vs extending a newly merged flag

I think extending the existing flag makes a lot of sense. I'll switch over to using that flag and part of the config 👍