Merge crusoe_update branch to main

[michal-cech]

crusoe_update branch is a successor branch to issues:

• Merge automation #1
• Integrate recommender system #2
• Integrate the dashboard updates #3

The required student updates were merged together with their corresponding original repository history. I went through Docker deployment and Vagrant & Ansible deployment. It should be deployable. The question is whether the components actually work together.

• docker-compose deploys everything
• Vagrant files deploying singular parts of the Crusoe to separate VMs work
• Common Vagrant file deploying everything in a single VM works

This also applies to the newly integrated component: the Recommender system - Dockerfile, separate Vagrantfile, and integration to common Vagrantfile.

[michal-cech]

Observations:

One observation:

Everything is super old: both Vagrantfiles and Dockerfiles are based on Debian 10.

This proved to be especially problematic when integrating the Recommender system, which requires a newer version of Python (Debian 10 has mainly Python 3.7, Recommender prerequisites need at least Python 3.10). This was not an issue for the Docker deployment, but had to be respected for Vagrant & Ansible deployment (mainly the common VM) - solvable by installing Python3.10 from source files and setting it as an alternative version.

What is a little more problematic (assuming the Recommender system and CRUSOE (observe) should work over the same Neo4J database). Crusoe observe deploys Neo4J 3.5.x, Recommender system seems to utilize queries with syntax compatible with 4.0+ versions. I did not change this; it was out of the scope of the issues from my PoV. Modernization will be a probably big task on its own.