[Snyk] Upgrade @textea/json-viewer from 3.5.0 to 4.0.1

[Madhuri-cs]

Snyk has created this PR to upgrade @textea/json-viewer from 3.5.0 to 4.0.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 2 versions ahead of your current version.

• The recommended version was released a year ago.

Release notes

Package name: @textea/json-viewer

• 4.0.1 - 2024-12-15
  

  4.0.1 (2024-12-15)

  Bug Fixes

  • update Object datatype for correct pluralization of Items (#531) (004e5c0)
• 4.0.0 - 2024-09-18
  

  4.0.0 (2024-09-15)

  For this major version, we switched from MUI v5 to v6. We also removed a few functions that were deprecated in V3.

  Please check the Migration Guide for more details.

  ⚠ BREAKING CHANGES

  • remove deprecated createDataType and displayObjectSize
  • migrate to MUI v6

  Features

  • migrate to MUI v6 (5ed7245)
  • remove deprecated createDataType and displayObjectSize (2923478)
• 3.5.0 - 2024-08-26
  

  3.5.0 (2024-08-26)

  Features

  • add data-key-toggle-* class name for customization (c1e605a)
  • add utils getPathValue (194ac43)
  • hide colon when key is empty (c1ce6ed)
  • passing path to Editor for better customizability (f03ab10)
  • support displayComma for showing comma (2c85bdb)

from @textea/json-viewer GitHub release notes

---

Important

• Warning: This PR contains a major version upgrade, and may be a breaking change.
• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[github-actions]

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Count (with fixes)	Without fixes	Threshold	Result
🔴 Critical Severity	0	0	10	✅ Passed
🟠 High Severity	4	0	25	✅ Passed
🟡 Medium Severity	5	24	500	✅ Passed
🔵 Low Severity	1	0	1000	✅ Passed

⏱️ SLA Breach Summary

⚠️ Warning: The following vulnerabilities have exceeded their SLA thresholds (days since publication).

Severity	Breaches (with fixes)	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	0	15 / 30 days	✅ Passed
🟠 High	0	0	30 / 120 days	✅ Passed
🟡 Medium	0	2	90 / 365 days	⚠️ Warning
🔵 Low	0	0	180 / 365 days	✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

• Critical without fixes: 0
• High without fixes: 0
• Medium without fixes: 24
• Low without fixes: 0

⚠️ BUILD PASSED WITH WARNINGS - SLA breaches detected for issues without available fixes

Consider reviewing these vulnerabilities when fixes become available.