Update Progenitor to 0.13 across Omicron crativerse

Going to need this for upcoming RFD 634-related improvements (particularly being able to refer to materialized Git ref files from Progenitor).

Update Progenitor, add progenitor-extras (must be published before any repo updates land):

• https://github.com/oxidecomputer/serde_tokenstream/pull/221
• -> https://github.com/oxidecomputer/progenitor/pull/1301
• -> release progenitor (above two are not strictly necessary but would be nice to have in progenitor 0.12)
• -> get progenitor-extras out
• figure out websockets vs HTTP/2 situation: https://github.com/oxidecomputer/oxide.rs/pull/1364#issuecomment-3947844351

Update repos to progenitor 0.13 and reqwest 0.13:

• omicron (MUST LAND before crucible so that progenitor-extras is available): https://github.com/oxidecomputer/omicron/pull/9917
• crucible: https://github.com/oxidecomputer/crucible/pull/1854
• dendrite: https://github.com/oxidecomputer/dendrite/pull/218
• maghemite: https://github.com/oxidecomputer/maghemite/pull/633
• propolis: https://github.com/oxidecomputer/propolis/pull/1046
• lldp: https://github.com/oxidecomputer/lldp/pull/50

Update Omicron to pull in updates for all these repos:

• TODO

Clean up progenitor < 0.13 references:

• dendrite
• maghemite
• propolis
• crucible
• omicron
• lldp

Open questions:

• Moving retry operation code from Omicron to Progenitor repo under progenitor-util. The code I currently have locally is generic over a RetryableError trait which is implemented for both progenitor 0.12.0 and an internal newtype wrapper in Omicron. An alternative is to release a progenitor-util 0.1.0 that's against progenitor 0.10.0 (used by crucible), and a progenitor-util 0.2.0 against progenitor 0.12.0. Need to consult with Adam on this. Addressed this by having two copies of this logic currently, one in Omicron and one in Progenitor. Once cleanup is complete, the Omicron-internal copy can be removed.