Fix method resolution bug when base class methods override getattr

[alexandervladsemenov]

This PR closes #610.

The issue was that the getattr method does not override methods from the base class. As a result, EarthAccessFile methods were inherited from the base class fsspec.spec.AbstractBufferedFile.

• To address this, getattribute is used instead of getattr. The implementation is designed to avoid infinite recursion.

• The base class has been changed from fsspec.spec.AbstractBufferedFile to io.IOBase to ensure correct reading from in-memory files using xarray.

• An additional test has been added to verify in-memory reading with xarray.

---

📚 Documentation preview 📚: https://earthaccess--1015.org.readthedocs.build/en/1015/

[github-actions]

👈 Launch a binder notebook on this branch for commit e4e7c82

I will automatically update this comment whenever this PR is modified

👈 Launch a binder notebook on this branch for commit d5377fc

👈 Launch a binder notebook on this branch for commit 8a7b220

👈 Launch a binder notebook on this branch for commit cb7d3d7

[itcarroll]

Thanks for the PR! I will work out how to make the integration-tests run on GitHub Actions.

@betolink @mfisher87 I'm surprised there is no previous test using xarray.open_*, so where should such a test go? This PR has it with tests/unit/test_store but it seems to me like a new file called tests/integration/test_xarray.py would be better.

[itcarroll]

Have confirmation from in zulipchat that test_earthaccess_xarray_access should be moved under tests/integration. I suggest a test_xarray module, and renaming to test_open_dataset.

[alexandervladsemenov]

Have confirmation from in zulipchat that test_earthaccess_xarray_access should be moved under tests/integration. I suggest a test_xarray module, and renaming to test_open_dataset.
@itcarroll I've created "test_xarray" integration test and pushed an update.