feat (HIS): add cyclomatic complexity check

[AfonsoSantos96]

This PR introduces the feature of checking the cyclomatic complexity of the HIS metrics in the ci.

Next is a list of the HIS metrics, indicating which checks are currently being supported, and what tools are being used to check each metric.

Metric	Decription	Supported	Tool
CALLING	Number of callers (<5)
CALLS	Number of called functions (<7)
COMF	Ratio of comments to statements (>=0.2)
CYC	Cyclomatic Complexity (<=10)	x	pmccabe
GOTO	Number of Goto (=0)
LEVEL	Number of nested conditions (<=4)
PARAMS	Number of function parameters (<=5)
PATH	Number of Paths (<80)
REC	Recursive Functions (=0)
RETURN	Number of returns in function (<=1)
STMT	Number of statements in function (<=50)
VOCF	Vocabulary of function (<=4)

The MISRA-related metrics are addressed by the separate misra check:

• NOMV: Violations of the HIS subset of MISRA C rules
• NOMVP: Violations of the HIS subset of MISRA C rules by rule

The following metrics are currently not addressed since they are related to
project evolution and cannot be evaluated in a single commit/snapshot:

• SCHG: Number of statements changed in project
• SDEL: Number of statements deleted in project
• SI: Stability index of project
• SNEW: Number of statements added in project

Checklist:

• The changes generate no new warnings when building the project. If so, I have justified above.
• I have run the CI checkers before submitting the PR to avoid unnecessary runs of the workflow.

[danielRep]

As previously pointed before on the first PR, some comments still stand and are not being addressed (that's why I didn't reviewed the main script). Please review according to the comments that me and @josecm pointed on the time:

Before running each metric, I think an output information should notice the user which metric is being "in the moment" checked.

• The script process all metrics file by file. This approach makes the output a mess. I will prefer that all files are processed metric by metric to have a sense of what is currently being tested.

I agree.

• In a case a specific file isn't complaint with some of the metrics, will the name of the file be printed? I can see that with cflow, but I'm asking if there are other cases with other tools where that isn't going to happen

Also agree. The metrics should always hide the output from the tools. I guess this is being done for some but not all. Are we intercepting stderr as well as stdout? On errors we should print the name of the file, the metric, the value calculated as well as the threshold.

I think it would be better to use regex instead of ad hoc parsing to process the output of each tool.

[danielRep]

Calling this from a root of a repo with the ci module, this won't run. Besides follow the same sintax as "license-check"

Suggested change

	his-check:
	@./his_checker.py $(_his_files)
	his_check_script:=$(ci_dir)/his_checker.py
	his-check:
	@$(his_check_script) $(_his_files)

[danielRep]

This is not needed. You should push the file with +x permissions.

[danielRep]

Suggested change

	CYCLOMATIC_TRESHOLD = 10
	CYCLOMATIC_THRESHOLD = 10

[danielRep]

Suggested change

	if colony_count > CYCLOMATIC_TRESHOLD:
	if colony_count > CYCLOMATIC_THRESHOLD:

[danielRep]

Suggested change

	print("Complexity exceeded (max." + str(CYCLOMATIC_TRESHOLD) + "): "
	print("Complexity exceeded (max." + str(CYCLOMATIC_THRESHOLD) + "): "