fix(pagination): support for pagination with logging enabled

[sufyankhanrao]

What

This PR fixes the api logging configuration by writing a __deep_copy__ method in the classes to handle the logger cloning as logger can't be pickled. Also, this commit narrows down the pagination type to be applied for subsequent calls after the 1 call.

Why

1. To fix the behavior of logging with pagination
2. To following the feature consistent across all languages by locking a pagination type

Closes #98

Type of change

Select multiple if applicable.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause a breaking change)
• Tests (adds or updates tests)
• Documentation (adds or updates documentation)
• Refactor (style improvements, performance improvements, code refactoring)
• Revert (reverts a commit)
• CI/Build (adds or updates a script, change in external dependencies)

Dependency Change

If a new dependency is being added, please ensure that it adheres to the following guideline https://github.com/apimatic/apimatic-codegen/wiki/Policy-of-adding-new-dependencies-in-the-core-libraries

Breaking change

If the PR is introducing a breaking change, please ensure that it adheres to the following guideline https://github.com/apimatic/apimatic-codegen/wiki/Guidelines-for-maintaining-core-libraries

Testing

List the steps that were taken to test the changes

Checklist

• My code follows the coding conventions
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added new unit tests

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud