Fix #627: Add SAFE to CI

[elbrujohalcon]

Description

Add SAFE to our CI pipelines.

Closes #627.

• I have read and understood the contributing guidelines

[elbrujohalcon]

We're safe now, @paulo-ferraz-oliveira @bormilan @NelsonVides !!

[bormilan]

Nice! I think we should make an issue to fix the problematic lines that you ignored now.

[elbrujohalcon]

Nice! I think we should make an issue to fix the problematic lines that you ignored now.

I don't think so. I reviewed each one of them and they are, in fact, safe... Even when using functions that can be abused, we know that they are not.

The calls to list_to_atom come from parsing Erlang modules that are not compiled. So, those atoms 100% not existing, but we do want to create them for our analysis.
The calls to file:consult/1 are needed in order to analyse config files and such... We could, in theory, check the size or whatever attribute from those files before running file:consult/1 on them... but... we'd end up calling file:consult/1, anyway... and I'm pretty sure that SAFE doesn't know if we checked the files before calling the function.

So... unavoidable ignores, all of them.