chore: cleanup tiling strategy comments for classes and tests

[drduhe]

Issue #, if available: n/a

Notes

• Cleaned up and added comments to unit tests for TestVariableTileTilingStrategy, TestVariableOverlapTilingStrategy, and TestTilingStrategy classes.
• Improved code readability, structure, and added detailed descriptions for each test case to clarify their purpose and expected behavior.

Changes:

1. Refactoring:

   • Added descriptive comments across all test cases to explain what each test validates.
   • Improved code organization with consistent spacing and formatting for better readability.
   • Ensured each section of the code is logically separated and easy to understand.
   • Added reST style PyDoc comments to class methods missing them.

2. Test Clarifications:

   • For TestVariableTileTilingStrategy and TestVariableOverlapTilingStrategy:
     • Added detailed explanations of tiling strategies and feature deconfliction processes.
     • Ensured all test scenarios cover expected cases (e.g., full image, ROI, tiny images, edge tiles).
   • For TestTilingStrategy:
     • Explained the different scenarios for generating crops with various overlaps and sizes.
     • Highlighted invalid configuration checks for the chip generator, ensuring appropriate error handling.

Checklist

Before you submit a pull request, please make sure you have the following:

• [x] Code changes are compact and well-structured to facilitate easy review
• [x] Changes are documented in the README.md and other relevant documentation pages
• [x] PR title and description accurately reflect the changes and are detailed enough for historical tracking
• [x] PR contains tests that cover all new code and the code has been manual tested
• [x] All new dependencies are declared (if any), and no unnecessary libraries are added
• [x] Performance impacts (if any) of the changes are evaluated and documented
• [x] Security implications of the changes (if any) are reviewed and addressed
• [x] I have read the Contributing Guidelines and agree to follow the Code of Conduct

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.