Prepare for 1.8.2 release

[Kirill888]

Reason for this pull request

1.8.1 had a regression in .geobox. It only applies to re-injected CRS data, but example notebooks do that, so this has been fixed and we need to make a new release soon. Getting some easy fixes in before that.

Proposed changes

• Extend allowed dtype enum with complex64, complex128

• Be robust when traversing lineage

• Understand location field in dataset document

• Document configure_s3_access in the api docs

• Some other documentation tweaks

• Closes 'NoneType' object has no attribute 'items' when indexing dataset. #988

• Closes Allow specifying dataset location from within the yaml document #990

• Tests added / passed

• Fully documented, including docs/about/whats_new.rst for all changes

[codecov]

Codecov Report

Merging #989 into develop will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #989      +/-   ##
===========================================
+ Coverage    92.98%   93.00%   +0.02%     
===========================================
  Files           97       97              
  Lines         9703     9733      +30     
===========================================
+ Hits          9022     9052      +30     
  Misses         681      681              

Impacted Files	Coverage Δ
datacube/utils/rio/_rio.py	100.00% <ø> (ø)
datacube/scripts/dataset.py	88.97% <100.00%> (+0.78%)	⬆️
datacube/utils/aws/__init__.py	100.00% <100.00%> (ø)
datacube/utils/documents.py	97.80% <100.00%> (+0.05%)	⬆️
datacube/utils/py.py	100.00% <100.00%> (ø)
datacube/utils/xarray_geoextensions.py	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dcab0e0...1963ae4. Read the comment docs.

[jeremyh]

I think we should pop the location(s) out of the document, similar to what's done with the lineage, since they're already stored separately in the DB (and are modified separately with other apis -- leaving possibly-inconsistent duplicate copies of the locations)

[Kirill888]

ok, I will then force it to be a string and not a list, because popping list will loose data as the rest of the code assume single uri when you first inject the dataset into DB