Emsarray

* Fix licence vs license confusion ([pull request 63](https://github.com/csiro-coasts/emsarray/pull/63))

* Add CF Convention attributes to coordinate variables when extracting points ([pull request 34](https://github.com/csiro-coasts/emsarray/pull/34))
* Reworked how command line entrypoints are discovered ([pull request 35](https://github.com/csiro-coasts/emsarray/pull/35))
* Added brief tutorial on writing command line Python scripts using emsarray ([pull request 35](https://github.com/csiro-coasts/emsarray/pull/35))
* Various documentation fixes ([pull request 42](https://github.com/csiro-coasts/emsarray/pull/42), [pull request #43](https://github.com/csiro-coasts/emsarray/pull/43), [pull request #52](https://github.com/csiro-coasts/emsarray/pull/52), [pull request #58](https://github.com/csiro-coasts/emsarray/pull/58))
* Added Python 3.11 support to CI ([pull request 44](https://github.com/csiro-coasts/emsarray/pull/44))
* Allow manual binding of conventions to datasets ([pull request 45](https://github.com/csiro-coasts/emsarray/pull/45))
* Renamed Format to [Convention](https://emsarray.readthedocs.io/en/v0.4.0/api/conventions/interface/#emsarray.conventions.Convention) ([pull request 46](https://github.com/csiro-coasts/emsarray/pull/46))
* Used [shapely.polygons()](https://shapely.readthedocs.io/en/stable/reference/shapely.polygons.html#shapely.polygons) when generating geometry. This results in a massive performance improvement. The minimum version of Shapely has been bumped to 2.0.0 ([pull request 47](https://github.com/csiro-coasts/emsarray/pull/47))
* Add [emsarray export-geometry](https://emsarray.readthedocs.io/en/v0.4.0/cli/#emsarray-export-geometry) command ([pull request 48](https://github.com/csiro-coasts/emsarray/pull/48))
* Use coordinate bounds from the dataset when making polygons ([pull request 49](https://github.com/csiro-coasts/emsarray/pull/49))
* Fix a bug in Ugrid.drop_geometry() ([pull request 50](https://github.com/csiro-coasts/emsarray/pull/50))
* Relicense to BSD 3-Clause ([issue 55](https://github.com/csiro-coasts/emsarray/issues/55), [pull request #56](https://github.com/csiro-coasts/emsarray/pull/56))
* Automate most of the release process ([pull request 60](https://github.com/csiro-coasts/emsarray/pull/60))
* Add a CITATION.cff file and example citation to the [FAQ](https://emsarray.readthedocs.io/en/v0.4.0/getting-started/faq/) ([issue #37](https://github.com/csiro-coasts/emsarray/issues/37), [pull request #38](https://github.com/csiro-coasts/emsarray/pull/38))

* Fixed ‘Release notes’ URL in setup.cfg package metadata

* Use variable and dimension names as-is, instead of casting to strings. [xarray](https://docs.xarray.dev/en/stable/index.html#module-xarray) internally treats all variable and dimension names as Hashable, without assuming they are strings. NetCDF4 files always use string names, so this change should not affect you if you only use NetCDF4 datasets ([pull request 25](https://github.com/csiro-coasts/emsarray/pull/25)).
* Fix error when UGRID start_index is the string “0” or “1”. The conventions imply this should be an integer type, however real datasets use a string value here so a tolerant implementation is useful ([pull request 26](https://github.com/csiro-coasts/emsarray/pull/26), [pull request csiro-coasts/emsarray-data#1](https://github.com/csiro-coasts/emsarray-data/pull/1)).
* Split emsarray.operations in to separate modules ([pull request 27](https://github.com/csiro-coasts/emsarray/pull/27)).
* Add [emsarray.operations.geometry](https://emsarray.readthedocs.io/en/v0.3.0/api/operations/geometry.html) module which can export dataset geometry to GeoJSON and Shapefiles ([pull request #28](https://github.com/csiro-coasts/emsarray/pull/28)).
* Add [Format.drop_geometry()](https://emsarray.readthedocs.io/en/v0.3.0/api/formats/interface.html#emsarray.formats.Format.drop_geometry) method ([pull request 29](https://github.com/csiro-coasts/emsarray/pull/29)).
* Add [emsarray.operations.point_extraction](https://emsarray.readthedocs.io/en/v0.3.0/api/operations/point_extraction.html) module and [emsarray extract-points](https://emsarray.readthedocs.io/en/v0.3.0/cli.html#emsarray-extract-points) command line entry point which can extract point data from a dataset ([pull request 29](https://github.com/csiro-coasts/emsarray/pull/29)).