Adding nested data retrieval for stats. Splitting up api endpoint and params...

This code change improves how the system handles nested data structures and API requests. Previously, the code expected simple field names like "repository_size", but now it can handle nested paths like "statistics/repository_size" by splitting the path and extracting the final part for storage. The system also switches from manually building URL query strings to using proper parameter dictionaries when making API calls, which is a cleaner and more reliable approach. These changes make the code more flexible for accessing deeply nested data and follow better practices for API communication.