Refactoring router to utilize get_session_context

[PtrBednarik]

#405

[gialmisi]

Is this really needed since calling SessionContext(user=..., db_session=...) is already equivalent to this?

[PtrBednarik]

Now, I think it is. Tests failed when I tried to use get_session_context() method at endpoint which do not contain request data. So I created a method, which does not require request parameter.
When I asked Chatbot for help, got answer like this -
"Because FastAPI dependencies must be callable, and you cannot use a union type RequestType as a dependency.
The only way to reuse the same context structure in endpoints without request data is to provide a dedicated dependency function."

But if is it wrong way of thinking, let me know.

[gialmisi]

I see, this makes sense then. I renamed the function to be more descriptive.

[gialmisi]

Good, thank you!

See PtrBednarik#4 (some changes I made while reviewing that should be incorporated). Please merge these into your branch when updating the PR. Check my comments for more details what needs to change. I might not have added a comment everywhere were a repeated issues has risen (e.g., with the missing docstrings), so please generalize when needed.

Some notes:

• Refrain from reducing the documentation level of the code. Now, in some places docstrings were completely removed, and in some places important comments were removed. I do not understand why?
• I suggest you setup pre-commit hooks, see https://desdeo.readthedocs.io/en/latest/tutorials/contributing/#pre-commit-hooks (feedback is welcomed on the section!)