Added API to reset forgotten password

[lukaskabc]

Mail server configuration is now required to start the application [code link].

[gitguardian]

⚠️ GitGuardian has uncovered 8 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	Generic High Entropy Secret	e2b5992	src/test/java/cz/cvut/kbss/termit/persistence/dao/PasswordChangeRequestDaoTest.java	View secret
-	-	Generic High Entropy Secret	e2b5992	src/test/java/cz/cvut/kbss/termit/persistence/dao/PasswordChangeRequestDaoTest.java	View secret
-	-	Generic High Entropy Secret	2a3c6b5	src/test/java/cz/cvut/kbss/termit/persistence/dao/PasswordChangeRequestDaoTest.java	View secret
-	-	Generic High Entropy Secret	79ad742	src/test/java/cz/cvut/kbss/termit/persistence/dao/PasswordChangeRequestDaoTest.java	View secret
-	-	Generic High Entropy Secret	2a3c6b5	src/test/java/cz/cvut/kbss/termit/persistence/dao/PasswordChangeRequestDaoTest.java	View secret
-	-	Generic High Entropy Secret	e2b5992	src/test/java/cz/cvut/kbss/termit/persistence/dao/PasswordChangeRequestDaoTest.java	View secret
-	-	Generic High Entropy Secret	79ad742	src/test/java/cz/cvut/kbss/termit/persistence/dao/PasswordChangeRequestDaoTest.java	View secret
-	-	Generic High Entropy Secret	e2b5992	src/test/java/cz/cvut/kbss/termit/persistence/dao/PasswordChangeRequestDaoTest.java	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[ledsoft]

See the inline comments.

[ledsoft]

Also, please always link the PR to the issue it resolves.

[ledsoft]

Implements kbss-cvut/termit-ui#332.

[ledsoft]

LGTM