[CI] run tics on weekly schedule

[sharder996]

Adds Tiobe's TICS github action to the Multipass project

• Runs on a weekly basis (the Desktop team SSDLC guide suggests nightly)
• Each analysis takes about 4+hrs to run (may vary depending on the number of changed files between runs)
• The TICS custom action has some specific requirements which are not always clear
  • The coverage report must be at ${{ github.workspace }}/coverage/coverage.xml
  • The project must be built beforehand with standard build tools and build directories
    • Build files should be in ${{ github.workspace }}/build
    • make must be used for compilation (using ninja generator will fail the action)
• TICS analysis now includes and analyzes the tests/ subdirectory (this is inline with similar projects such as Mir)
• Current metrics from test runs can be found here

---

MULTI-1759

---

Closes #3962

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.44%. Comparing base (3d1d7f6) to head (ac69de0).
⚠️ Report is 379 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3953   +/-   ##
=======================================
  Coverage   89.44%   89.44%           
=======================================
  Files         259      259           
  Lines       14758    14758           
=======================================
  Hits        13200    13200           
  Misses       1558     1558           

☔ 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.

[ricab]

Hey Scott, it looks like there is an issue with tools folder: https://canonical.tiobe.com/tiobeweb/TICS/TqiDashboard.html#axes=Project(multipass),Sub()&metric=tqiTestCoverage&sel=Sub(tools)

[sharder996]

@ricab I think its out of my control. I can see the same "error" in the initial TICS run that was run by Tiobe staff. Comparing between the different time stamps, I've noticed some times slight changes between runs even though the source code was the same. I also Tiobe is actively developing the backend of TICS and analysis results may be subject to changes. The TICS github action used here is simply a client that calls some backend API endpoint.

https://canonical.tiobe.com/tiobeweb/TICS/TqiDashboard.html#axes=Project(multipass),Date(1715703041),Sub()&metric=tqiTestCoverage&sort=T(1,worst)

[ricab]

Thanks Scott, I have a few questions.

[ricab]

Could you please explain why --preserve-env was necessary?

[ricab]

And why not update? Are these runner's apt cache guaranteed to be up to date?

[sharder996]

This is how Mir had it set up so I copied it, but I just tested and it isn't necessary. The variables that --preserve-env is protecting isn't related to building Multipass anyways.

[ricab]

OK, makes sense. How about the missing apt update?

[Saviq]

We have this b/c:
https://github.com/canonical/mir/blob/df6674bd3686286aa0e422fdc26664e1fbef5adf/.github/workflows/tics.yml#L24-L25

You might get hit with some dependency that requires configuration, and the install will seem stuck b/c it will wait on user input.

[sharder996]

No reason to exclude it so I added it back.

[ricab]

I see, interesting. Thanks @Saviq, is this only a concern in these runners? I suppose GH could be addressing that under the hood.

@sharder996, might be a good idea to do the same then (i.e. avoid apt-get asking what services should be restarted.)

[ricab]

Thanks @sharder996, this looks good to me now!

As discussed, we have a little margin to speed up with ccache if we need to in the future. Otherwise just needs a rebase.