Repository maintenance

[jptosso]

• Add README #5
• Add magefile: run benchmark, change coraza version #6
• Add CI basic tests #7
• Add GA to post results of benchmark changes in PR #8
• Automatically update coraza version GA #9
• Merge https://github.com/jptosso/coraza-benchmark-2 here #10 <-- contains modsecurity comparison and more profiles
• Remove coraza v2? It is irrelevant now #11
• Integrate with www.coraza.io #12
• Create additional profiles #13
• add renovatebot config #14

Ping @s3rj1k @fzipi @jcchavezs @M4tteoP

[s3rj1k]

We had a quick talk regarding CI before with @fzipi.
I can take this, but needs a bit more discussion on what exactly we want to check there.

[jptosso]

@s3rj1k it's up for discussion, but I think we should cover tests and run the benchmark making sure that all bechmarks are run.
Also, I think we should deprecate v2 benchmarks, as it is not supported anymore and the comparison is irrelevant

[s3rj1k]

deprecate v2 benchmarks

we can add that it's not supported but I would like to keep them as long as possible for reference, this reference has real value for project support because of huge performance increase that can be verified locally

[fzipi]

Found this one that might help: https://github.com/marketplace/actions/continuous-benchmark

[s3rj1k]

We actually don't have go benchmarks there, documentation is wrong about that, we run go application that computes time between stages and produces CSV.

I've done quick docker magic to showcase how it works, just in case we want a demo:

git clone -b docker https://github.com/s3rj1k/coraza-benchmark.git 
cd coraza-benchmark
docker run --rm -v $(pwd)/tests:/opt/coraza-benchmark/tests -v $(pwd)/waf.rules:/opt/coraza-benchmark/waf.rules docker.io/s3rj1k/coraza-benchmark -rules=/opt/coraza-benchmark/waf.rules