[Chore] Refactor the controllers to reduce coupling and improve naming

[malparty]

Issue

The AppController in the Laravel application handles too many things.

This has several impacts on the project:

• The controller has too many responsibilities (list users, manage keywords, and initiate the spider app)
• The name of the controller does not give clues about its role
• The name of the actions cannot be a simple verb (see this table as an example, but different verbs can be used) as commonly seen in controller actions names
• The generated API documentation does not group the endpoints by model, which makes it harder to read

Expected

• The application must ship with smaller controllers, each scoped to a single model
• The names of the actions in the controllers must be verbs and must be consistent across controllers

[mgmgpyaesonewin]

Refactor ( #19 )

• Updated routes to use KeywordController and SpiderController for improved functionality handling.
• Updated docs for route groups