Refactoring (#1201)

* Some initial refactoring

* Make it one application

* Got it working

* Fix problem on Windows

* Move WebWolf

* Move first lesson

* Moved all lessons

* Fix pom.xml

* Fix tests

* Add option to initialize a lesson

This way we can create content for each user inside a lesson. The initialize method will be called when a new user is created or when a lesson reset happens

* Clean up pom.xml files

* Remove fetching labels based on language.

We only support English at the moment, all the lesson explanations are written in English which makes it very difficult to translate. If we only had labels it would make sense to support multiple languages

* Fix SonarLint issues

* And move it all to the main project

* Fix for documentation paths

* Fix pom warnings

* Remove PMD as it does not work

* Update release notes about refactoring

Update release notes about refactoring

Update release notes about refactoring

* Fix lesson template

* Update release notes

* Keep it in the same repo in Dockerhub

* Update documentation to show how the connection is obtained.

Resolves: #1180

* Rename all integration tests

* Remove command from Dockerfile

* Simplify GitHub actions

Currently, we use a separate actions for pull-requests and branch build.
This is now consolidated in one action.
The PR action triggers always, it now only trigger when the PR is
opened and not in draft.
Running all platforms on a branch build is a bit too much, it is better
 to only run all platforms when someone opens a PR.

* Remove duplicate entry from release notes

* Add explicit registry for base image

* Lesson scanner not working when fat jar

When running the fat jar we have to take into account we
are reading from the jar file and not the filesystem. In
this case you cannot use `getFile` for example.

* added info in README and fixed release docker

* changed base image and added ignore file

Co-authored-by: Zubcevic.com <rene@zubcevic.com>

src/main/resources/lessons/csrf/documentation/CSRF_intro.adoc

@@ -0,0 +1,27 @@
+=== What is a Cross-site request forgery?
+
+Cross-site request forgery, also known as one-click attack or session riding and abbreviated as CSRF
+(sometimes pronounced sea-surf) or XSRF, is a type of malicious exploit of a website where unauthorized commands are transmitted
+from a user that the website trusts. Unlike cross-site scripting (XSS), which exploits the trust a user has for a particular site, CSRF
+exploits the trust that a site has in a user's browser.
+
+A cross-site request forgery is a 'confused deputy' attack against a web browser. CSRF commonly has the following characteristics:
+
+* It involves sites that rely on a user's identity.
+* It exploits the site's trust in that identity.
+* It tricks the user's browser into sending HTTP requests to a target site.
+* It involves HTTP requests that have side effects.
+
+At risk are web applications that perform actions based on input from trusted and authenticated users without requiring the user to authorize
+the specific action. A user who is authenticated by a cookie saved in the user's web browser could unknowingly send an HTTP request to a site
+that trusts the user and thereby causes an unwanted action.
+
+A CSRF attack targets/abuses basic web functionality. If the site allows that causes a state change on the server, such as changing the victim's email address or password, or purchasing
+something. Forcing the victim to retrieve data doesn't benefit an attacker because the attacker doesn't receive the response, the victim does.
+As such, CSRF attacks target state-changing requests.
+
+Let's continue with some exercises to address way to perform a CSRF request.
+
+
+
+