Update docs/Requirements.md to add OO as a must have

Setup a tool for pre-commit hook (husky) to apply linting before commit

Suggestion of implementation for study: implement the interface segregation principle in dishes logic for:

• Repeatable and NonRepeatable dishes
• Type of dishes
• Implement logic to prevent NonRepeatable dishes from being added to order more than once instead of remove them after the insertion

Document rules for async dojo

Configure code to use environment variables

Improve README.md with:

• Short description of the project
• Requirements
• Instructions on how to use
• Instructions on how to contribute

Suggestion: add a docs folder to keep track of the decisions made as the project evolves.

Configure github actions to run tests on each push

We must define the main responsibility of the Meal class, which is creating an order and printing its meals, I strongly believe that the Meal class should be responsible for creating an order that includes: extracting and ordering the input, building the correct dish, and adding it to order.
I think the printing step must be outside the Meal class, maybe in the BakeryService class or even in a presenter.

Fix peer dependencies error