Change the --timeout flag to time the entire deployment rather than a single helm install / upgrade

[AustinAbro321]

Is your feature request related to a problem? Please describe.

Currently the timeout flag on zarf package deploy is used only for helm. A deployment fails if any of the helm installs or upgrades take longer than the given timeout or the default timeout of 15 minutes. We plan to extend the timeout flag in #2678 to for use in health checks on components.

This behavior may be confusing for users, theoretically the command zarf package deploy --timeout 15m can last for hours depending on how many helm installs take place. It may be better for the timeout to simply fail when the zarf package deploy takes longer than the submitted timeout. Ideally this change would occur during the v1 release where breaking changes will be more expected.

We must consider if there should be a default value in this case. A Zarf package can be complex and take hours to deploy without anything going wrong. Large image pushes, for example, can take a long time depending on the network of the environment.