Copying markdown docs for contexts into schema files

[kriswest]

Pr that migrates context docs from markdown files into a schema. The markdown files still exists for the time being - we hope to try an generate markdown pages or directly render documentation pages from these schemas so that we can go full circle (and then delete the hand-maintained markdown docs in favour of generated).

partially resolves #1032

[netlify]

✅ Deploy Preview for fdc3 canceled.

Name	Link
🔨 Latest commit	78bcfa3
🔍 Latest deploy log	https://app.netlify.com/sites/fdc3/deploys/64ff19bda2a3ae0008fe2c17

[robmoffat]

nice work, @kriswest

[hampshanubs]

@kriswest Great idea.

[kriswest]

@robmoffat @mistryvinay @hughtroeger I think I'm done - all context types now have docs for all fields I believe. I've regenerated the TypeScript types, which look better now that all fields have titles - although there are still a few Purples and Fluffys - these occur because quicktype seems to treat top-level types and references differently, generating a duplicate where a context is referenced elsewhere. There may be a workaround possible by referencing all contexts in some other schema just used to do generation (meaning all are references, none are top-level). Will explore when I have time - until then, or until quicktype improves, we'll have to live with them.

These changes will need a review and merge. They should not be changing the standard, just improving the docs.

@robmoffat should be all the feed material needed to look at rendering docs from context schemas.

[kriswest]

Thanks @hughtroeger, fixes applied for your review.

@mistryvinay and @finos/fdc3-maintainers I need a review from you to merge this. Most obvious change will be that there are now docs for generated typescript files that will show up in VSCode and other editors (yay) - all are drawn from the Markdown docs that we hope to replace (with rendering from schema files) in future.

[kriswest]

@hughtroeger please also be aware of/review the following commit I just added to this PR which finally explains our use of JSON schema to define Context types and bridging messages:
1d29027

[mistryvinay]

LGTM - thanks for putting this together Kris. 🚀

Missing nav entries were resolved - dismissing review so we can merge.