Author Readme files for each library and integrate into the PyPi descriptions. Fixes #156

[Chris Mullins (cleemullins)]

Fixes #156

Following guidance found on Python Packaging

This means:

• Added a new readme.md file for each package
• Added the readme contents to the package via the .toml file, per current guidance in the Python world.

As we move forward, updating the package descriptions is just a change to the relevant readme files.

[tracyboehrer (tracyboehrer)]

Chris Mullins (@cleemullins) Food for thought, not a no... I had originally played with providing sample code in these README's, then decided it was a doc maintenance problem. What about just links to Learn documents so that samples (etc) is in one place?

[Chris Mullins (cleemullins)]

I had originally played with providing sample code in these README's, then decided it was a doc maintenance problem.

Reasonable, but the samples (and really all the readme) is generated by an LLM on analysis of our repo. There's no hand-rolled samples or code in there.

Now, if we were spiffy, we would auto generate the entire readme from a template on each merge to main. Using a readme.md template, this seems practical. I started going down that route, but would have spent more time doing that (by far) than just using a prompt and generating them.

[Rodrigo Brandão (rodrigobr-msft)]

There is a lot of code here, and this is a more accessible (more visible) source of examples than even our samples. For that reason, I think we should treat the code examples here the same. If we are going to provide this much code in our READMEs on PyPI, then I would make sure it's well tested. I haven't looked through all of the READMEs to save time because it also don't feel right to verify this code via inspection alone.