Simplify and publish progress of Committee Specs

[chet-ensign]

Suggestion from Bret Jordan:

I keep thinking about our naming and numbering systems we have here at OASIS and how we could make them easier. I wonder if all CSDs need to have a vote, or just the ones that will become public review docs or CSs.

It would be great IMHO if we had a document landing page that listed each draft that was released and then just "flagged" the ones that were approved by the TC and the date they were approved on.

Example:

Committee Specification Draft 01
Committee Specification Draft 02
Committee Specification Draft 03 - Approved on 2020-08-01, Sent for Public Review on 2020-08-10
Committee Specification Draft 04 - Approved on 2020-09-10
Committee Specification Draft 05
Committee Specification Draft 06
Committee Specification Draft 07 - Approved on 2020-10-01, Sent for Public Review on 2020-10-10
Committee Specification Draft 08 - Non-material changes from public review
Committee Specification 01 - Approved on 2020-10-20
Committee Specification Draft 09
Committee Specification Draft 10 - Approved on 2020-11-01, Sent for Public Review on 2020-11-10
Committee Specification Draft 11 - Non-material changes from public review
Committee Specification 02 - Approved on 2020-11-30
Committee Specification 02 - Submitted as COS 2020-12-10
OASIS Standard 2021-02-20

This way the editors are ONLY ever releasing CSDs "drafts" and the TCs can vote on them when they want to approve them and accept them. I think we should also look at further simplifications to the templates to make them more friendly for non-word based solutions like Markdown.