compatible: dpe-6306 add common static code analysis

[paulomach]

Common workflow for static code analysis
Tested on mysql-vm

Obs: Unit test coverage on dashboard includes code not belonging to the repo, i.e. code from a library not belonging to the charm is accounted in the code coverage. I am in contact with Tiobe to see how to fix it Tracking issue on TICSISSUES-35

[carlcsaposs-canonical]

The tiobe/tics-github-action seems to already provide a reusable component that handles most of the complexity

I'm hesitant to wrap that reusable component (as opposed to using that reusable component directly), and I don't think a reusable workflow adds much value on top of the already reusable component

Some of the issues that come with wrapping a reusable component:

1. Versioning
   If we pin a version of tiobe/tics-github-action, anytime we change the version it's a breaking change
   If we passthrough the version of tiobe/tics-github-action, Renovate will not detect updates correctly and we have to create custom renovate config to update the input so that it recognizes the value is for tiobe/tics-github-action
2. Inputs need to be wrapped. If we support multiple versions of tiobe/tics-github-action, the inputs might not be compatible with all versions or could have different meanings

Furthermore, the contents of this reusable workflow seem to be around tox config and the format of unit test coverage exports—which I think can be quite repo-specific, and given the simplicity of those elements in the workflow, I think it'd be better off for that to be in the repo itself, where it can be modified as needed

I think it'd be best to standardize on naming & contents for the workflow and then copy-paste it across our repos