Chore/update dockerfiles

[nXtCyberNet]

Proposed changes

• Updated all Docker base images to their latest patched versions
• Updated Go dependencies to patched versions to address security and maintenance updates
• No functional or behavioral changes are introduced
  Fixes Security: Vulnerability Scan Results for litmusportal-auth-server #5313
  Fixes seclog: [HIGH] Multiple Critical Dependencies with Known Vulnerabilities Detected #5336

---

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.

• I have read the [CONTRIBUTING](https://github.com/litmuschaos/litmus/blob/master/CONTRIBUTING.md) 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 (not applicable)
• I have added necessary documentation (not applicable)

---

Dependency

• None

---

Special notes for your reviewer

• This PR intentionally keeps the scope limited to base image and Go dependency patch updates
• No runtime or functional behavior is affected
• Frontend Dockerfile note: The current frontend Dockerfile assumes that npm build artifacts are already present in the build context, which is not feasible in clean CI or reproducible builds. A multi-stage Docker build would allow the frontend build to be executed inside the container, producing a self-contained image. I have not included this change here to keep the scope focused, but I can submit a follow-up PR if this approach is acceptable.

[nXtCyberNet]

any updates?

[Jonsy13]

Hi @nXtCyberNet Can you resolve the conflicts, PR looks good, Would like to see PR checks running!

[nXtCyberNet]

Hi @nXtCyberNet Can you resolve the conflicts, PR looks good, Would like to see PR checks running!

resolved the merged conflicts ,