Code coverage support

[froozeify]

This PR add code coverage support for plugin.

By default the coverage is not enabled.

For a better output, plugin can extract the report to automatically create a comment on the PR with the report in md format.

Interconnected PR :

• Code coverage support #49
• ci: add code coverage support pluginsGLPI/empty#56

Whatsapp plugin got a dedicated PR to test the modification (see in the feed under for the link)

Screenshot

Once the project is merged on main you got comparison otherwise (whatsapp branch) :

Test PR with simulated code into main

https://github.com/glpi-network/whatsapp-wcoverage/pull/2

Test PR targeting not the default branch (coverage should not be run)

https://github.com/glpi-network/whatsapp-wcoverage/pull/3

[froozeify]

We should create a dedicated config file. For example .glpi-coverage.json

If the file is not present or if his field enabled is false we don't run code coverage.

Enabled field is optional, value is true by default. For glpi-empty, we would be able like that to set it has example with enabled: false

This file would should contain something like

{
  "enabled": true,
  "lower_threshold": 50,
  "upper_threshold": 75,
  "fail_below_min": false
}

We should probably also create a generic action for the code coverage report config in that case. (if feasible)
This will avoid to have to put that config on every plugin : https://github.com/glpi-network/whatsapp/pull/32/changes#diff-c471496bcb3ed47397b73d2e3e3aa41a8a679c86accaed9e05676fd9d5987434R41-R70

[froozeify]

@stonebuzz @Rom1-B

Small issue reported to me by @cedric-anne is that currently the new coverage comparison is done only based on the plugin default main branch artifact.

Some plugin could have 2 "main" branch one for 10.x and one for 11.x so the coverage difference could be biased.

We should see if it will have a big impact, supporting both based on PR would probably mean an even bigger ci code for check/updating those artifacts. (Probably not possible to trigger artifact refresh on target branch before running the ci and coverage on current pr, not sure github support synchronous run like that)

[Rom1-B]

In that case, perhaps the simplest solution would be to run it only with the main branch? So, don't display anything with 10.0./bugfixes.

[froozeify]

I've updated to run coverage only when the default branch is targeted.

[Rom1-B]

Please rebase

[froozeify]

On it, pushed accidentally before rebase ;)