ci: configure TICS workflow

[britneywwc]

Note: uncomment PR action trigger before merging

Done

• Added TIOBE config file: tiobe_config.txt
• Added GH workflow to update TICS coverage: tics_coverage.yaml
  • The workflow runs coverage tests for python and js files on build-coverage. The coverage report is then uploaded as an artifact
  • The TICS action downloads the GH artifact and publishes it on TICS Viewer

QA

• See TICS Analysis and coverage action passes, specifically TICS (22.x)
• Check on TICS Viewer that the "Measured on" date is updated
• Check that TQI score has increased from the screenshot before workflow integration

Issue / Card

Fixes WD-30653 and WD-30654

Screenshots

[webteam-app]

Demo

Jenkins

demos.haus

[britneywwc]

For QA. Remove pull_request and uncomment before merging

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.20%. Comparing base (068b523) to head (889f4d5).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2117   +/-   ##
=======================================
  Coverage   77.20%   77.20%           
=======================================
  Files          16       16           
  Lines        1676     1676           
=======================================
  Hits         1294     1294           
  Misses        382      382           

Flag	Coverage Δ
python	77.20% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[immortalcodes]

Thanks for this PR. The dashboard looks good, I have mostly exploratory comments.

[immortalcodes]

Could you help me understand this commands better, as far as I know the coverage is already calculated in other test workflows, what's different here?

[muhammad-ali-pk]

These commands run coverage on python code locally, and generate coverage outpul in xml format.
The coverage calculated in other workflows is on the PR itself. The reason for doing it here is on the main branch of repo, which is going to run every week.

[immortalcodes]

I don't see templates on the dashboard, is that expected?

[muhammad-ali-pk]

Not expected, it should be included.
I have updated the tiobe config, so it should now be generated.