Refactor the references of project everywhere and rename "algorithm system(s)" to "algorithm(s)"

[robbertbos]

Description

Before the demo, there was a request to change at least any visible mentions of projects to the algorithm system. In the UI, everything is changed, but technically, everything is still called project(s).

Based on the feedback we received during the first demos, we realized that algorithm systems would result in people asking questions about what we mean precisely with an algorithm system. Although algorithm is too narrow, it will be a better match. It will align with "Algoritmekader" and "Algoritmeregister".

Implementation notes

• Rename "algorithm system(s)" to "algorithm(s)": routing, breadcrumps, info on pages, create algorithm page, etc.
• Refactor code base and model to use "algorithm(s)" instead of "project(s)"

Remark: With this change we have an algorithm with a systemcard with algorithms. This flow needs to be fixed.