Update CI and doc - fix for DataArrays

[aulemahal]

Fixes #224, fixes #225 , fixes #227.

• Accepts DataArray in Regridder and SpatialAverager for both ds_in and ds_out, they are simply converted to _temp_dataset before doing anything. A trivial test was added.
• Expands the CI jobs to python 3.10 ~and 3.11~. A specific version of ESMpy was pinned for each version.
  • 3.11 was removed as numba (a dependency) is not yet compatible
  • I also removed the CI trigger on "push" (except for master). It was triggering all builds in duplicate when opening a pull request. Now, only pull requests and the master branch will have CI runs.
  • Push the upstream build to use python 3.10.
• Updated the installation page
  • Remove reference to specific python version
  • Remove warning for ESMF and mpi. I believe this was an issue before we put esmpy>=8.0 as a dependency.
  • Add new deps.
  • Remove note that pip is limited to 0.3
  • Add notes about ESMpy 8.4
• Updated the doc
  • Bumped the version number to 0.7.0.
  • Dynamical year and add "and the xESMF development team" to the copyright.
  • Mock import for esmpy.

[aulemahal]

@raphaeldussin Do you know what are those "build (3.7) Expected" entries in the checks? I think they never get updated since I changed the build names, but I can't find where these entries are set to update them...

Maybe @Zeitsperre knows about this.

[Zeitsperre]

@raphaeldussin Do you know what are those "build (3.7) Expected" entries in the checks? I think they never get updated since I changed the build names, but I can't find where these entries are set to update them...

Maybe @Zeitsperre knows about this.

In the branch settings, at some point, someone with maintainer access marked some CI actions as necessary in order to merge to the main development branch. This need to be updated to use the existing CI jobs instead.

[aulemahal]

Ok thanks @Zeitsperre ! I don't have access to that I believe.

[huard]

Removed expected builds from checks