Add --context option to crossplane cli beta trace command

[padlar]

Allows the user to run trace command without switching Kubernetes context.

Description of your changes

Fixes #5537

I have:

• Read and followed Crossplane's contribution process.
• Run make reviewable to ensure this PR is ready for review.
• Added or updated unit tests.
• Added or updated e2e tests.
• Linked a PR or a docs tracking issue to document this change.
• Added backport release-x.y labels to auto-backport this PR.

Need help with this checklist? See the cheat sheet.

[phisco]

Thanks @padlar!

[jbw976]

was just thinking if there were other commands this could also benefit fro a --context argument. I think maybe crossplane beta top would be the only one?

all current commands:

  xpkg build        Build a new package.
  xpkg install      Install a package in a control plane.
  xpkg login        Login to the default package registry.
  xpkg logout       Logout of the default package registry.
  xpkg push         Push a package to a registry.
  xpkg update       Update a package in a control plane.
  beta convert deployment-runtime
                    Convert a ControllerConfig to a DeploymentRuntimeConfig.
  beta convert pipeline-composition
                    Convert a Patch-and-Transform Composition to a Function
                    Pipeline Composition.
  beta render       Render a composite resource (XR).
  beta top          Display resource (CPU/memory) usage by Crossplane related
                    pods.
  beta trace        Trace a Crossplane resource to get a detailed output of its
                    relationships, helpful for troubleshooting.
  beta xpkg init    Initialize a new package from a template.
  beta validate     Validate Crossplane resources.

[brovoca]

Really nice to see this incorporated this quick! Waiting for next release 🤩