Change VerificationChain

[bitPogo]

📌 References

• Issue: Consider alternative Assertion pattern #80, Optimise Runtime #91
• Related PRs: Add mockery #3, Add examples #4

What does the PR achieve/Which part improves the PR?

This renames the exiting VerificationChain into StrictVerificationChain (which is hybrid of verification and assertion) and adds a new VerificationChain to preserve the already existing behaviour. Also expectation methods do not bleed into the code anymore.

🤔 DOD Checklist

• My code passes the lint checks.
• My changes are covered with proper tests.
• All tests are pass.
• My changes update the documentation.
• My changes are reflected in the changelog.

[github-actions]

	Warnings
⚠️	Changes should be reflected in the CHANGELOG.adoc
⚠️	Too Big Pull-Request, keep changes smaller

Generated by 🚫 Danger Kotlin against dce7446