Improve Package Approval Time

[liamfallon]

The package approval time is long for packages in Porch, especially for packages with complex KPT pipelines and PackageVariantSets.

This issue should be addressed in Porch:

1. Improve package approval time
2. Improve logging and feedback so that package developers and testers can see where the package approval time budget is being expended

See also:
#462

The package approval time seems to be at least partly a function of the functionality in the deployed packages (certainly in the case of cluster creation) and of the time it takes for the KPT functions in the package pipeline to run in the case of PackageVariants.

For the end to end tests, we could perhaps do some operations in parallel (such as creating the regional, edge01, and edge02 clusters), but this could load the test infrastructure.

Regarding PackageVariantSets and PackageVariants, care should be taken by the developers of these packages to take care to design efficient kpt functions so that the package approval time is not too slow.

Regarding this issue, in the Porch architecture for R3, the package approval time cannot easily be improved.