SOR - Service - Refactor to improve readability and maintainability

[brunoguerios]

Code could be better organized to make it easier to onboard other team members, so more people are able to provide proper support.

Suggestions:

1. rename functions so they are easier to differentiate (e.g. getSorSwapPaths, getSwapPathsFromSor, sorGetPathsWithPools, etc.)
2. separate helper from main functions is a more clear way (e.g. break into separate files)
3. better separate sorv1 from sorv2 implementation
4. restructure files/folders (considering there will be not only pools for v2 and v3, but also hooks for v3 soon)
5. ...