resolve missing experiment pod logs issue

[harshit12339]

Proposed changes

This PR fixes #5044 and fixes #5077
that we were also facing here in flipkart, that experiment logs were not showing on UI.

The backend has the actual keys of experimentPod, which were mistakenly put as faultPod in frontend, due to which experiment logs came missing on UI.
refer the screenshot, for backend graphql api response under getExperimentRun api response -> executionData - chaosData
https://github.com/litmuschaos/litmus/blob/master/chaoscenter/graphql/server/pkg/chaos_experiment/types.go#L55

Screenshot-

Types of changes

What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

• New feature (non-breaking change which adds functionality)
• Bugfix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices applies)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• I have signed the commit for DCO to be passed.
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have added necessary documentation (if appropriate)

Dependency

• https://github.com/litmuschaos/litmus/pull/5198/files
  In above pr, the changes were done to make logs readable, and hence will enable experiment logs under Chaos logs under their parent key instead of opaque [object Object].

[Copilot]

Pull Request Overview

This PR fixes a bug where experiment pod logs were not displaying correctly in the UI due to incorrect property names. The backend GraphQL API uses experimentPod as the key, but the frontend was incorrectly referencing faultPod, causing experiment logs to be missing from the UI.

• Updated TypeScript interface to use correct property name experimentPod instead of faultPod
• Fixed component references to use the correct property for accessing experiment pod logs
• Ensured consistency between frontend and backend API schema

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
chaoscenter/web/src/api/entities/workflowRun.ts	Updated ChaosData interface to use correct experimentPod property name
chaoscenter/web/src/views/ExperimentRunDetailsPanel/ExperimentRunDetailsPanel.tsx	Fixed key prop to reference correct experimentPod property
chaoscenter/web/src/controllers/CustomStepLog/CustomStepLog.tsx	Updated expPod parameter to use correct experimentPod property

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Pull Request Overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[amityt]

Hi @harshit12339, thanks for the contribution! The attached screenshot shows the API response. Could you please share another screenshot showing the UI rendering the logs that were previously not visible?

[harshit12339]

Hi @harshit12339, thanks for the contribution! The attached screenshot shows the API response. Could you please share another screenshot showing the UI rendering the logs that were previously not visible?

Hi @amityt thanks for your review, attaching experiment pod logs which werent visible previously.