FIX: Use openpyxl instead of xlrd

Fixes #29 (closed)

Summary

Removes the dependency on the discontinued xlrd<=1.2, uses xlrd>=2.0 for xls files and openpyxl for xlsx files.

Focus

Apparently we waited long enough so that Pandas fixed their engines for reading xls(x) files when both xlrd and openpyxl are installed. So only added a unittest for xls files and removed the version limitation

Test Environment

Simply do the unittests and the integrationtests with the updated xlrd version.

Check List for the Author

Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines

• All automated tests pass
• Reference related Issues
• Up-to-date CHANGELOG.md
• Annotations in code (Gitlab comments)
  • Intent of new code
  • Problems with old code
  • Why this implementation?

Check List for the Reviewer

• I understand the intent of this MR
• All automated tests pass
• Up-to-date CHANGELOG.md
• The test environment setup works and the intended behavior is reproducible in the test environment
• In-code documentation and comments are up-to-date.
• Check: Are there spezifications? Are they satisfied?

For further good practices have a look at our review guidelines.

CHANGELOG.md

@@ -55,6 +55,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Fixed ###
 - An exception in collect_information does no longer lead to a break down.
+- Removed dependency on discontiued xlrd version
 * Fixed an issue where `caosadvancedtools.cache.UpdateCache` would
   cause an `sqlite3.IntegrityError` if more than one change was cached
   for the same entity.