Implement the articles API

[Capure]

This should cover adding, editing, retrieving, and removing articles.

The code must check and enforce proper permissions.

Request validation should be in place.

The business logic should take into account the likes and reads system.

Because the courses API doesn't exist yet, the functionality related to that can be skipped for now, but keep it in mind while designing the articles API.

The extent of included unit and integration tests should be determined with reason keeping in mind the scale and scope of the project.

Appropriate frontend tooling to access the new API should be provided. In particular, an SDK should allow the frontend application to add, edit, delete, and fetch the articles, with the fetching being done server-side for faster load times.

[Capure]

Contact me for additional information in case you need help.

[Capure]

I highly recommend aggregating multiple people to this issue, due to the sheer size and scope of it.

Moreover, we currently do not have a proper way of conducting user auth, the suggested solution will require connecting to the original Bajton backend, thus I recommend delegating this part to me or @0ZeroFive5 as we already have the required knowledge of the project's architecture.