feat(HIS): add GOTO his metric

[AfonsoSantos96]

This PR introduces the feature of checking the existence of a goto statement in a function/file.
According to the HIS metrics, no goto statement is allowed
The qmcalc tool is used to check this metric.
This tool only outputs the existence of a goto expression in the file, so our tool output won't specify the function where the expression is used, only highlighting the file where the expression is used.

---

Edited by @danielRep :
To test with https://github.com/bao-project/bao-his-tests just run the command make ci METRIC=goto.

Checklist:

• Tested using the bao-his-tests repo.
• Compared and validated outputs to ECLAIR his metrics assessment on bao-his-tests repo
• 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]

Tested and it LGTM.

[danielRep]

Updated with the modifications introduced in #68 and changed the output format.

@miguelafsilva5 @josecm
Use the testing repo (https://github.com/bao-project/bao-his-tests) has a dummy testbed for each individual metric verified by the HIS checker.
You only need to clone the repo, checkout the ci to this branch, and then make ci METRIC=goto.

[miguelafsilva5]

Tested using the repo provided by @danielRep. From my observations, it seems to be working as intended.
The only corner case that might have mislead results that I found was hiding the goto statement in a macro (e.g #define HIDING goto). Then using that macro in other files is not detected as a goto statement. The checker only points to the original file where it is define and not where it is used. Furthermore, if said macro is not used, the checker also fails saying that a goto statement is present.
However, since the threshold is 0, it is should not be a problem.

[danielRep]

Tested using the repo provided by @danielRep. From my observations, it seems to be working as intended. The only corner case that might have mislead results that I found was hiding the goto statement in a macro (e.g #define HIDING goto). Then using that macro in other files is not detected as a goto statement. The checker only points to the original file where it is define and not where it is used. Furthermore, if said macro is not used, the checker also fails saying that a goto statement is present. However, since the threshold is 0, it is should not be a problem.

That's a corner case that the tool would not detect. For such corner cases we would need to have a specific implementation.