add support for 418 for dubious queries

[ildyria]

The goal of this is to flag queries which are just bots trying to scan for vulnerabilities.

Combined with Fail2Ban, we can now ban IP then to avoid being hit uselessly by such visitors.

read more here:
https://aureola.codes/en/blog/2021/how-stop-vulnaribility-scanners-laravel-fail2ban

/etc/fail2ban/filter.d/nginx-honeypot.conf

[Definition]
failregex = ^<HOST>.*"(GET|POST).*" (418) .*$
ignoreregex =

/etc/fail2ban/jail.d/honeypot.conf

[nginx-honeypot]
enabled = true
filter = nginx-honeypot
port = http,https
logpath = /var/log/nginx/access.log
maxretry = 1

Of course in the case of Apache we need to check the respective log.

As said in the article:

What you can achieve is that you get less unwanted traffic. No more and no less. Also, you may be able to prevent vulnerabilities from being found that would otherwise have been discovered.

[codecov]

Codecov Report

Merging #1875 (abf5c42) into master (607c763) will decrease coverage by 0.24%.
The diff coverage is 100.00%.

Additional details and impacted files

[qwerty287]

I don't really like the matching system, but I don't have any other idea

[qwerty287]

Not really related: We could actually add a security.txt to Lychee to easily allow researchers to report vulns to us.