List plugins deactivated for context unset and context delete

[chandrareddyp]

What this PR does / why we need it

This pull request enhances the user experience for the tanzu context delete and tanzu context unset commands by listing all installed plugins as deactivated.

Which issue(s) this PR fixes

Fixes #

Describe testing done for PR

1. E2E tests are updated to test the `tanzu context unset `and `tanzu context delete` use cases.

2. Manual testing has done, below are the details for `tanzu context unset `and `tanzu context delete` use cases
❯ t context create --endpoint unstable.tmc-dev.cloud.vmware.com --staging  --name tmc2   
Flag --name has been deprecated, it has been replaced by using an argument to the command
[i] API token env var is set

[ok] successfully created a TMC context
[i] Checking for required plugins...
[i] Installing plugin 'account:v0.1.3' with target 'mission-control'
[i] Plugin binary for 'account:v0.1.3' found in cache
[i] Installing plugin 'iam:v0.1.3' with target 'mission-control'
[i] Plugin binary for 'iam:v0.1.3' found in cache
[i] Installing plugin 'cluster:v0.1.6' with target 'mission-control'
[i] Plugin binary for 'cluster:v0.1.6' found in cache
[i] Successfully installed all required plugins
❯ 
❯ t context unset tmc2
The context tmc2 for the target mission-control has been set as inactive
Deactivating plugin 'continuousdelivery:v0.1.3' for context 'tmc2'
Deactivating plugin 'data-protection:v0.1.3' for context 'tmc2'
Deactivating plugin 'secret:v0.1.3' for context 'tmc2'
Deactivating plugin 'workspace:v0.1.5' for context 'tmc2'
Deactivating plugin 'audit:v0.1.3' for context 'tmc2'
Deactivating plugin 'helm:v0.1.3' for context 'tmc2'
Deactivating plugin 'policy:v0.1.3' for context 'tmc2'
Deactivating plugin 'tanzupackage:v0.2.2' for context 'tmc2'
Deactivating plugin 'clustergroup:v0.1.3' for context 'tmc2'
Deactivating plugin 'provider-aks-cluster:v0.1.3' for context 'tmc2'
Deactivating plugin 'events:v0.1.3' for context 'tmc2'
Deactivating plugin 'inspection:v0.1.3' for context 'tmc2'
Deactivating plugin 'apply:v0.3.0' for context 'tmc2'
Deactivating plugin 'agentartifacts:v0.1.3' for context 'tmc2'
Deactivating plugin 'integration:v0.1.3' for context 'tmc2'
Deactivating plugin 'management-cluster:v0.1.3' for context 'tmc2'
Deactivating plugin 'ekscluster:v0.1.3' for context 'tmc2'
Deactivating plugin 'provider-eks-cluster:v0.1.3' for context 'tmc2'
Deactivating plugin 'setting:v0.2.1' for context 'tmc2'
Deactivating plugin 'aks-cluster:v0.1.6' for context 'tmc2'
❯
❯ t context delete tmc2
Deleting the context entry from the config will remove it from the list of tracked contexts. You will need to use `tanzu context create` to re-create this context. Are you sure you want to continue? [y/N]: y
[i] Deleting entry for cluster tmc2
❯ 
❯ t context create --endpoint unstable.tmc-dev.cloud.vmware.com --staging  --name tmc2
Flag --name has been deprecated, it has been replaced by using an argument to the command
[i] API token env var is set

[ok] successfully created a TMC context
[i] Checking for required plugins...
[i] Installing plugin 'cluster:v0.1.6' with target 'mission-control'
[i] Plugin binary for 'cluster:v0.1.6' found in cache
[i] Installing plugin 'iam:v0.1.3' with target 'mission-control'
[i] Plugin binary for 'iam:v0.1.3' found in cache
[i] Installing plugin 'account:v0.1.3' with target 'mission-control'
[i] Plugin binary for 'account:v0.1.3' found in cache
[i] Successfully installed all required plugins
❯ t context delete tmc2
Deleting the context entry from the config will remove it from the list of tracked contexts. You will need to use `tanzu context create` to re-create this context. Are you sure you want to continue? [y/N]: y
[i] Deleting entry for cluster tmc2
Deactivating plugin 'audit:v0.1.3' for context 'tmc2'
Deactivating plugin 'helm:v0.1.3' for context 'tmc2'
Deactivating plugin 'policy:v0.1.3' for context 'tmc2'
Deactivating plugin 'continuousdelivery:v0.1.3' for context 'tmc2'
Deactivating plugin 'data-protection:v0.1.3' for context 'tmc2'
Deactivating plugin 'secret:v0.1.3' for context 'tmc2'
Deactivating plugin 'workspace:v0.1.5' for context 'tmc2'
Deactivating plugin 'inspection:v0.1.3' for context 'tmc2'
Deactivating plugin 'apply:v0.3.0' for context 'tmc2'
Deactivating plugin 'tanzupackage:v0.2.2' for context 'tmc2'
Deactivating plugin 'clustergroup:v0.1.3' for context 'tmc2'
Deactivating plugin 'provider-aks-cluster:v0.1.3' for context 'tmc2'
Deactivating plugin 'events:v0.1.3' for context 'tmc2'
Deactivating plugin 'agentartifacts:v0.1.3' for context 'tmc2'
Deactivating plugin 'integration:v0.1.3' for context 'tmc2'
Deactivating plugin 'management-cluster:v0.1.3' for context 'tmc2'
Deactivating plugin 'provider-eks-cluster:v0.1.3' for context 'tmc2'
Deactivating plugin 'setting:v0.2.1' for context 'tmc2'
Deactivating plugin 'aks-cluster:v0.1.6' for context 'tmc2'
Deactivating plugin 'ekscluster:v0.1.3' for context 'tmc2'
❯ 

Release note

The UX has been updated for the `tanzu context delete` and `tanzu context unset` commands to list plugins that are being deactivated.

Additional information

Special notes for your reviewer

[marckhouzam]

This looks good and addresses the original request of adding the list of plugins that are being deactivated when doing context unset and context delete.

However, with this improvement we probably want to be consistent and do something similar in other cases. Specifically:

1. tanzu context use and tanzu context create do not list the plugins that become active, if they are already installed
   • so if I do tanzu context unset mycontext I now get the list of plugin that are deactivated, but if I do immediately after tanzu context use mycontext I only see [i] All required plugins are already installed and up-to-date
2. similarly, when for those same tanzu context use and tanzu context create, if there was another active context before, we do not show the plugins that are being deactivated from the old context and replaced by the plugins from the new context.

That second point should be discussed as it may be showing too much information

[marckhouzam]

This needs a rebase.
Also, could you add a release note in the PR description? This change is an improvment to end-users and should be mentioned.

After that, LGTM
Thanks!

[chandrareddyp]

This looks good and addresses the original request of adding the list of plugins that are being deactivated when doing context unset and context delete.

However, with this improvement we probably want to be consistent and do something similar in other cases. Specifically:

1. tanzu context use and tanzu context create do not list the plugins that become active, if they are already installed

   • so if I do tanzu context unset mycontext I now get the list of plugin that are deactivated, but if I do immediately after tanzu context use mycontext I only see [i] All required plugins are already installed and up-to-date

2. similarly, when for those same tanzu context use and tanzu context create, if there was another active context before, we do not show the plugins that are being deactivated from the old context and replaced by the plugins from the new context.

That second point should be discussed as it may be showing too much information

As discussed created a separate issue #509 to handle context create and use, use cases.