Fix bug #332 and update instructions

[artificialfintelligence]

Your checklist for this pull request

Thank you for submitting a pull request! To speed up the review process, please follow this checklist:

• My Pull Request is small and focused on one topic so it can be reviewed easily
• My code follows the style guidelines of this project (make format)
• Commit messages are detailed
• I have performed a self-review of my code
• I commented hard-to-understand parts of my code
• I updated the documentation (docstrings, /docs)
• My changes generate no new warnings (or explain any new warnings and why they're ok)
• I have added tests that prove my fix is effective or that my feature works
• All tests pass when I run pytest tests (offline mode)

Description

Fixes bug #332 with the identified solution mentioned in the issue report.

[artificialfintelligence]

@20001LastOrder I'd appreciate it if you or @Eyobyb could independently verify that the modified Dockerfile works correctly before merging.

[20001LastOrder]

Looks good to me. Thanks for updating the documentation. We are also trying to find a way to integrate this into the poetry install process.

[artificialfintelligence]

@20001LastOrder Speaking of Poetry, in the documentation, that step 6 that I added does not cover the Poetry installation route 😣 It will install outside the Poetry virtualenv. I forgot to include the alternative poetry run python -m spacy download en_core_web_sm (as with step 5 above it). Should I create a new branch and everything?