Refactor Suggestion for Improved Configuration Handling in ailab-db

The current implementation of packages involves direct retrieval of configuration variables using `os.environ.get`. This approach, while functional, limits the flexibility and testability of the packages. The proposal is to refactor these packages so that functions requiring configuration data receive them as parameters, instead of directly accessing environment variables.

### Objectives:

1. **Enhanced Flexibility**: By passing configuration variables as parameters, we allow users to provide these values in ways that best suit their environment and use case, be it through environment variables, configuration files, or other means.

2. **Improved Testability**: Functions that explicitly accept configuration parameters are easier to test, as they do not rely on the external environment's state. This makes writing unit tests more straightforward and reliable.

3. **Clear Dependencies**: Having functions request necessary configuration as parameters makes the code more self-explanatory and clear about its dependencies.

### Proposed Changes:

- Refactor functions to accept configuration variables as parameters.
- Update documentation to reflect these changes and guide users on how to pass these parameters.
- Implement default values or error handling for cases where critical configuration data is not provided.
- Write unit tests to cover different scenarios, including those with varying configuration inputs.

### Action Items:

- [ ] Identify all instances where `os.environ.get` is used for configuration in the packages.
- [ ] Redesign these functions to accept configuration data as parameters.
- [ ] Update and test each function to ensure it operates correctly with the new parameter-based configuration.
- [ ] Revise the package documentation to clearly explain the new method of passing configuration data.
- [ ] Create and run unit tests to validate functionality and handle edge cases.