DM-32801: Add sphinx docs build action

[timj]

Checklist

• ran Jenkins
• added a release note for user-visible changes to doc/changes

[codecov]

Codecov Report

Merging #109 (9ba4fc8) into main (e1fd236) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #109   +/-   ##
=======================================
  Coverage   91.27%   91.28%           
=======================================
  Files          36       36           
  Lines        2154     2156    +2     
=======================================
+ Hits         1966     1968    +2     
  Misses        188      188           

Impacted Files	Coverage Δ
python/lsst/utils/_forwarded.py	75.00% <ø> (ø)
python/lsst/utils/inheritDoc.py	27.27% <ø> (ø)
python/lsst/utils/logging.py	81.55% <ø> (ø)
python/lsst/utils/tests.py	74.68% <ø> (ø)
python/lsst/utils/timer.py	96.26% <ø> (ø)
python/lsst/utils/__init__.py	100.00% <100.00%> (ø)
python/lsst/utils/backtrace/__init__.py	83.33% <100.00%> (+1.51%)	⬆️

---

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 e1fd236...9ba4fc8. Read the comment docs.

[ktlim]

I'm a little worried about all of the style/lint changes going on informally without a clear roadmap or policy, but this looks OK.

[timj]

Most of the fixes here are fixing legitimate problems with the numpydoc so I'm not sure what the problem is.

[ktlim]

pydocstyle has not been formally adopted (and barely even suggested, to my knowledge) as a tool for checking/verifying our docs. I agree that it can help us get rid of a lot of warnings and other problems, but we still shouldn't add it in random places without a clear roadmap.

[timj]

Right, but the usage here is consistent with the dev guide isn't it? What we haven't done is formalized the list of warnings that should be used -- the ones here and in daf_butler are adhoc.