Helm rollback, the workloads are deployed to the default namespace instead of the namespace where the rollback was executed.

[pgaijin66]

Describe the bug
A clear and concise description of what the bug is.

• Helm rollback done via k9s, rolls back workloads on default namespace.
• k9s show helm rollback worked, but does not say which namespace rollback was performed.

To Reproduce
Steps to reproduce the behavior:

1. Deploy helm to a namespace other than default
2. Deploy version 2 on the same namespace
3. Use k9s to rollback to previous verson

Historical Documents
When applicable please include any supporting artifacts: k9s debug logs, configurations, resource manifests, ...

Expected behavior
A clear and concise description of what you expected to happen.

• Workloads should be deployed to same namespace where rollback was done, not on default namespace
• Good to show the helm release details i.e namespace rollback is performed on as part of the rollback confirmation.

Screenshots
If applicable, add screenshots to help explain your problem.

Versions (please complete the following information):

• OS: [e.g. OSX]
  OSX

• K9s: [e.g. 0.1.0]
  k9s version
  ____ .______
  | |/ / __ _____
  | < ____ / /
  | | \ / /_ \
  ||__ \ ///___ >
  / /

Version: v0.32.3
Commit: 0021311
Date: 2024-03-06T06:35:12Z

• K8s: [e.g. 1.11.0]
  1.24

Additional context
Add any other context about the problem here.

[wjiec]

related PR #2652.