doc: publish the graphics enablement doc on rtd

[mattkae]

What's new?

• Transferred the Mir bringup guide to a how-to guide in the Mir project
  • Rewrote the document with a focus on graphics-core22. @RAOF please let me know if any of my assumptions about graphics-core22 were incorrect here, since the original document was intended for graphics-core20
• Published the document on readthedocs

How to test?

• Open the file in CI

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.35%. Comparing base (25ade62) to head (06e3b30).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3334      +/-   ##
==========================================
- Coverage   77.36%   77.35%   -0.01%     
==========================================
  Files        1075     1075              
  Lines       68268    68268              
==========================================
- Hits        52813    52812       -1     
- Misses      15455    15456       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[RAOF]

Comments inline

[mattkae]

@RAOF Can you expand a bit more on the following comments, not sure how to address:

• doc: publish the graphics enablement doc on rtd #3334 (comment)
• doc: publish the graphics enablement doc on rtd #3334 (comment)

[RAOF]

Oh, whoops! I totally missed that we didn't really update for any of the graphics-core22 changes on my first pass through!

That makes it both easier and harder. This is our only documentation on creating a provider snap, and it's a little bare, but perhaps what should be done here is to link out to that and improve it?

Then remove (or, really, move into a better provider creating document) everything from

## How to assemble a `graphics-core22` provider snap

until

## How to test a `graphics-core22` provider snap

[mattkae]

That makes it both easier and harder. This is our only documentation on creating a provider snap, and it's a little bare, but perhaps what should be done here is to link out to that and improve it?

Then remove (or, really, move into a better provider creating document) everything from

## How to assemble a `graphics-core22` provider snap

until

## How to test a `graphics-core22` provider snap

Why would we link out to that though? Shouldn't this document be the document on creating a provider snap, while the other one gets merged into this?

[RAOF]

If you need help doing or testing a libmali provider, I can poke at it.

[RAOF]

Couple of minor changes, but I think we've got the big stuff!

[mattkae]

@RAOF Committed the requested changes and cleaned up the history 🎉

[RAOF]

👍