COMMUNITY: Update Release Path & Incorporate Documents

[ChristopherA]

We have a release path for projects https://github.com/BlockchainCommons/Community/blob/master/release-path-standards.md

• [ ] Should we revise our categories to be more like COSS (as per https://specs.status.im). For instance, we don't have a deprecated category. [ALSO APPLY THAT TO OLDER Release Path]

But for projects like the Psuedonymity Guide, which have both, we may want to a different naming standards.

@shannona @namcios

[namcios]

Per @shannona :

My vision is something that "Drafting"/"Completed"/"Edited"/"Reviewed", maybe using slightly different words.

In which:

Edited: v0.9.0 Reviewed: v1.0.0 (implies walking through the whole process and making sure it all works right.)

[shannona]

I'll follow that up with a draft PR for our release article as time allows.

[shannona]

This needs to also accomodate when things move beyond Research (and where they go)