feat: add dirty-waters to CI

[randomicecube]

cc @monperrus @Stamp9

Relates to INRIA/spoon#5216, chains-project/dirty-waters#37, chains-project/dirty-waters#58

Key notes:

• x_to_fail parameter: the percentage of a single non-high severity issue present among the dependencies for the CI to break. It defaults to 5%, so what should it be here?
• comment_on_commit: whether the reports are allowed to be pasted as comments in the commits, in the case of high-severity issues breaking CI. Defaults to false, what do we want here?
• allow_pr_comments: whether the reports are allowed to be pasted as comments in pull requests. Defaults to true, what do we want here?
• By default, only static analysis happens. Do we want differential to be performed in certain scenarios too? If so, which ones?
• Gradual reporting is enabled by default -- only one of the reported smells has its table displayed per time, with the higher severity issues showing up first.
• Which maven build commands should be ran before running the dirty-waters action (if any)?

For more information on the action, see the wiki.

[monperrus]

all defaults here to feel how this works.