Remove Blossoms from Frontend

[andreicristian97]

Summary

• Removed text in the guided tour that referenced blossoms.
• Removed code in frontend that would award blossoms to the user at the end of the guided tour.

Basics

• The PR is rebased with current master
• I added a line to changelog.md
• Details of what I changed are in the commit messages
• References to issues, e.g. close #X, are in the commit messages and changelog
• The buildserver is happy

Checklist

• I fully described what my PR does in the documentation
• I fixed all affected documentation
• I fixed the introduction tour
• I wrote migrations in a way that they are compatible with already present data
• I fixed all affected decisions
• I added automated tests or a manual test protocol
• I added code comments, logging, and assertions as appropriate
• I translated all strings visible to the user
• I mentioned every code or binary not directly written or done by me in reuse syntax
• I created left-over issues for things that are still to be done
• Code is conforming to our Architecture
• Code is conforming to our Guidelines
• Code is consistent to our Design Decisions
• Exceptions to any guidelines are documented

First Time Checklist

• I have installed and I am using pre-commit hooks
• I am using Tailwind CSS Linting

Review

• I've tested the code
• I've read through the whole code
• I've read through the whole documentation
• I've checked conformity to guidelines
• I've checked conformity to requirements
• I've checked that the requirements are tested

[andreicristian97]

One open question:
As it is currently intended for the Blossoms to be reintroduced later, the relevant code pieces were left commented in the components with a comment explaining the situation. Is this ok or should the code be fully removed right now?

[hatchla]

• I've tested the code
• I've read through the whole code
• I've read through the whole documentation
• I've checked conformity to guidelines
• I've checked conformity to requirements
• I've checked that the requirements are tested

[markus2330]

As it is currently intended for the Blossoms to be reintroduced later, the relevant code pieces were left commented in the components with a comment explaining the situation. Is this ok or should the code be fully removed right now?

It would be better to completely remove it, git easily allows to restore it anyway.

A TODO in the code is definitely not needed as it would be a completely new feature if ever reintroduced.

[andreicristian97]

As it is currently intended for the Blossoms to be reintroduced later, the relevant code pieces were left commented in the components with a comment explaining the situation. Is this ok or should the code be fully removed right now?

It would be better to completely remove it, git easily allows to restore it anyway.

A TODO in the code is definitely not needed as it would be a completely new feature if ever reintroduced.

Commented code has been removed.

What is still present are the other files relevant to blossoms: gainBlossom.ts and the translation files blossoms.json
Should they be removed as well as they are currently not used?

[markus2330]

Yes, please go ahead and remove everything you found related to blossoms (except of backend, where we leave it for now).

[andreicristian97]

Removed all blossom-related files and references from the Frontend

[andreicristian97]

jenkins build please

[chr-schr]

👍

• I've tested the code
• I've read through the whole code
• I've read through the whole documentation
• I've checked conformity to guidelines
• I've checked conformity to requirements
• I've checked that the requirements are tested