spread links to login, logout, auth, rooms, enrollment, etc to the router

most of these features doesn't have a btn in the browsable api, so we need to make it more browsable, applying HATEOAS concept would enhance the user experience i guess

The issue mentions enhancing the browsable API with HATEOAS links for login, logout, auth, rooms, and enrollment. Start by examining the router configuration and the API views to understand the current endpoint structure. Look for where hyperlinks are generated in the browsable API, likely in serializers or view sets. The goal is to add missing links to these features so they appear in the API interface.

Written by the indexing model from the issue text.