refactor(tests): replace K8sExecInPod with AssertCommand for consistency in test assertions

[abhashsolanki18]

Purpose of PR?:

Fixes #1643

Does this PR introduce a breaking change?
No
If the changes in this PR are manually verified, list down the scenarios covered::

1. Verified that the K8sExecInPod calls were successfully replaced with AssertCommand without impacting test results.
2. Confirmed that permissions and expected outputs are consistent with the new implementation.
3. Ensured that refactored code retains functionality across all test cases.

Additional information for reviewer? : This PR is part of the refactoring effort to standardize test execution methods. It follows up on a previous PR where initial AssertCommand replacements were introduced.
Mention if this PR is part of any design or a continuation of previous PRs

Checklist:

• Bug fix. Fixes CI(tests) Use AssertCommand function in every test #1643
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• PR Title follows the convention of <type>(<scope>): <subject>
• Commit has unit tests
• Commit has integration tests

[abhashsolanki18]

hey @daemon1024 @rootxrishabh please approve the workflows and review this.

[abhashsolanki18]

hey @rootxrishabh last time the checks failed because of some typo, i have fixed it and pushed the changes, please approve the workflows and let me know if you find anything else that needs to be fixed.

[abhashsolanki18]

hey @daemon1024 @rootxrishabh @PrimalPimmy if anyone of you can approve the workflow and review this, so that i get to know if everything is working fine with the changes.

[daemon1024]

Can we debug the tests and make them passing?

[abhashsolanki18]

hey @daemon1024 i have fixed the errors occured in the tests, now they should succeed as expected. please approve the workflows. thanks.

[rksharma95]

@abhashsolanki18 there are some other issues as well that we're facing in CI, we're working on it, once it's fixed i will revert back here.