DRIVERS-2789 Convert Unified Test Spec to Markdown

[blink1073]

Please complete the following before merging:

• Update changelog.
• Make sure there are generated JSON files from the YAML test files.
• Test changes in at least one language driver.
• Test these changes against all server versions and topologies (including standalone, replica set, sharded
  clusters, and serverless).

[blink1073]

I had to remove a dead link to https://emptysqua.re/blog/mongodb-testing-network-errors/.

[jmikola]

Couple of suggestions but nothing I'd need to follow up on.

[jmikola]

I overlooked this in previous PRs but there's no way we can retain Definition Lists here, since it's non-standard syntax, correct?

[blink1073]

Correct, it doesn't render:

First Term
: This is the definition of the first term.

Second Term
: This is one definition of the second term.
: This is another definition of the second term.

[jmikola]

https://spec.commonmark.org/0.29/#example-631 suggests the trailing slash is used for a hard line break. I can see doing that for the "Schema version" highlights (although the bold text should already make them stand out), but why here and other entries with non-formatted text?

[blink1073]

I'm not sure why pandoc chose to do that

[jmikola]

I had to remove a dead link to https://emptysqua.re/blog/mongodb-testing-network-errors/

@ajdavis: FYI, that article still comes up on your blog's search widget, but there's no icon for it and the page is a 404.

[ajdavis]

Oops, I restored that article to my site now. I (wrongly?) thought it was obsolete and deleted it a while ago.

[jmikola]

@blink1073: I just realized that various internal link targets in the converted Unified Test Format spec were changed to (<>). I assume that was unintentional, but is it a common problem with the RST-to-MD conversions?

[blink1073]

The original doc had [observeEvents](<>), the conversion must not know what to do with that syntax.

[ajdavis]

I'm unsubscribing, if you need me for anything LMK.

[jmikola]

The original doc had observeEvents, the conversion must not know what to do with that syntax.

This seems related to original RST links to internal page anchors.

`storeEventsAsEntities <entity_client_storeEventsAsEntities_>`_

...was changed to:

[storeEventsAsEntities](<>)

Assuming this wasn't the only spec affected, can you check for this in any outstanding PRs? For things that were already merged, I suppose it can be handled in a follow-up ticket within the epic. The broken links should definitely not remain as-is.