Consider splitting this into two repos

[aguschin]

We can split this into two separate repos, connected via CI/CD:

1. One with lstm-model package, training scripts, Dockerfile.pipeline and DVC
2. Another with Flask application, Heroku, Dockerfile.app, docker-compose.yml

This may help with clarity and also be an example of connecting two repos. Of course, in this case we won't support the monorepo. This could create extra work of splitting CI/CD, so it may be better to decide on this before that work has been started. Beside that, we'll have to update all links in "practical materials" sections and all videos with repo discussion if we record some.

CI/CD then could like this:

1. When model should be updated (code changes, new data, schedule), CI is run in the 1st repo.
2. Upon completion, this CI updates references to the model in the 2nd repo.
3. Created commit triggers CI/CD in the 2nd repo, which run testing and re-deploys the REST API service with the new model.