docs: clarify detail about which global flags may be declared in config file

[timblaktu]

This issue is a follow-up on this conversation in defenseunicorns/uds-package-dubbd#279 about a minor inconsistency in the documentation about which CLI args can be declared in a zarf config file. In response to this footnote:

@Racer159 said:

This isn't entirely true - sub items (like package.create.output_directory) can be configured too, but --confirm is explicitly excluded to encourage interactive deployments and reviews of packages (if it were hidden in a zarf-config file less experienced users may not get the option to review a deployment to see if they are deploying (or removing!) the correct package.

I believe this page needs to be changed from this:

Users can configure the zarf init, zarf package create, zarf package deploy command flags, as well as any global flags, through a config file.

to this:

Users can configure the zarf init, zarf package create, zarf package deploy command flags, as well as most¹ global flags, through a config file.

Footnotes

1. Noting that only global zarf options may be declared, and that --confirm is not a global option. ↩