update axios package and relock

[ravi712]

Success criteria

Please describe what should be possible after this change. List all individual items on a separate line.

• Build should be successful and application should work as it was.

How to test

Please describe the individual steps on how a peer can test your change.

1. Sanity testing

Security

• Possible injection vector
• Authentication/Access controls touched
• Sensitive Data could be exposed
• XSS
• Logging/Monitoring touched
• Exchanges data with external systems
• No security implications

Additional considerations

• This PR might have performance implications

Documentation Considerations

These are hints for the documentation team to help write the docs.

[graymalkin77]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[Copilot]

Pull request overview

Updates the project’s Axios dependency version as part of a dependency refresh/relock effort.

Changes:

• Bump axios from 1.12.2 to 1.13.5 in package.json

[Copilot]

The PR title mentions a relock, but only package.json is changed in this diff. Without committing the corresponding lockfile update (e.g., package-lock.json / yarn.lock / pnpm-lock.yaml), installs/CI may continue resolving the previous Axios version or produce inconsistent dependency trees. Please include the updated lockfile generated by a clean install after the version bump.