Add linting workflow

[eliykat]

🎟️ Tracking

📔 Objective

📸 Screenshots

⏰ Reminders before review

• Contributor guidelines followed
• All formatters and local linters executed and passed
• Written new unit and / or integration tests where applicable
• Used internationalization (i18n) for all UI strings
• CI builds passed
• Communicated to DevOps any deployment requirements
• Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 7.72%. Comparing base (3715df4) to head (26f9cc0).

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@          Coverage Diff          @@
##            main    #719   +/-   ##
=====================================
  Coverage   7.72%   7.72%           
=====================================
  Files         68      68           
  Lines       2757    2757           
  Branches     477     477           
=====================================
  Hits         213     213           
  Misses      2529    2529           
  Partials      15      15           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

Checkmarx One – Scan Summary & Details – 4fcc2d1f-9378-40c0-bf99-6b5876d2d1b0

New Issues (3)

Checkmarx found the following issues in this Pull Request

Severity	Issue	Source File / Package	Checkmarx Insight
	CVE-2025-6558	Npm-electron-34.5.8	details Recommended version: 37.2.3 Description: Insufficient validation of untrusted input in ANGLE and GPU in Google Chrome prior to 138.0.7204.157 allowed a remote attacker to potentially perfo... Attack Vector: NETWORK Attack Complexity: LOW ID: ZwBaZGAu1WDQnZZEmR6my0uY3vuykTQ%2BTfc4k9UDg8g%3D Vulnerable Package
	CVE-2025-7656	Npm-electron-34.5.8	details Recommended version: 37.2.3 Description: An Integer Overflow vulnerability in V8 in Google Chrome prior to 138.0.7204.157 allowed a remote attacker to potentially exploit heap corruption v... Attack Vector: NETWORK Attack Complexity: LOW ID: 0VbIFFF8egLWhUfc3EveIR8Z16mLb6lPKQWTDpRCaPE%3D Vulnerable Package
	CVE-2025-7657	Npm-electron-34.5.8	details Recommended version: 37.2.3 Description: Use After Free in WebRTC in Google Chrome prior to 138.0.7204.157 allowed a remote attacker to potentially exploit heap corruption via a crafted HT... Attack Vector: NETWORK Attack Complexity: LOW ID: %2FHMCAP0EEPbBZVifKKZbRjwOPUakx2M5qsV7Srw7Les%3D Vulnerable Package

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud