kpt live destroy command should be able to wait for resources to be removed

[mortent]

The kpt live destroy command currently doesn't have parity with the kpt live apply command. In particular two pieces stand out:

• It doesn't allow the --prune-propagation-policy and --prune-timeout flags that allow users to specify whether we should wait for resources to be deleted, and if so, for how long.
• The Applier.Run function returns an init event on the channel with information about which resources will be applied/pruned. This is used by the table UI to be able to create the list of resources and their state before any changes are made. The Deployer should use a similar solution.

[aravindtga]

This has been partially addressed upstream and partially remains in kpt:

1. Init event for table UI - Fixed in cli-utils via Refactor destroyer to use tasks kubernetes-sigs/cli-utils#366. The Destroyer now emits InitEvent with ActionGroups before execution begins, enabling the table UI to display resources before changes are made.

2. --delete-propagation-policy and --delete-timeout flags - Still missing from kpt live destroy. The underlying cli-utils DestroyerOptions supports DeletePropagationPolicy and DeleteTimeout (also added in PR Refactor destroyer to use tasks kubernetes-sigs/cli-utils#366), but kpt doesn't expose these as CLI flags. By contrast, kpt live apply already has the equivalent --prune-propagation-policy and --prune-timeout (Added in Add --delete-propagation-policy and --delete-timeout flags to kpt live destroy #4665).