feat: human readable sbom integration

[jarebear6expepjozn6rakjq5iczi3irqwphcvb]

this commit adds a build process for SBOM markdown files triggered by the docs build process.

From your review in the previous implementation:

Could we maybe make it so the human-friendly SBOM formats are generated only for the readthedocs site (e.g. run the >sbom to markdown conversion in doc/Makefile) but not checked in to github as md files every week?

The sbom/Makefile is triggered in doc/Makefile.

I like this one!

[jarebear6expepjozn6rakjq5iczi3irqwphcvb]

fixes issue #2850

[terriko]

Approving tests to run now. This looks like what I was hoping for, but I'll let the linters and stuff do their job before coming back to review.

[jarebear6expepjozn6rakjq5iczi3irqwphcvb]

I've not added to the requirements.csv before and it is obviously different than the requirements.txt. How is that usually updated? Just add sbom2doc ?

[terriko]

You'll need to edit the doc/requirements.csv to add sbom2doc. The csv filet gives us a place to add the {vendor, product} pair for looking up CVEs. In this case, I'm rather sure sbom2doc doesn't have any yet, so you'd probably use the following pair in the file, similar to what I did in the main requirements.csv file:

anthonyharrison_not_in_db,sbom2doc

[terriko]

Approving tests to run again. I think this should be the last time and we might be ready to merge, but I'll let the tests do their work first.

[terriko]

Looks like we're ready to merge! Thanks for iterating on this one a few times as we figured out the best way to do it, and congratulations on your first merged commit!

[jarebear6expepjozn6rakjq5iczi3irqwphcvb]

Thank you!