Output a "fully rendered" markdown document

[pmolodo]

...that has been processed through pandoc.

The input and output format are both .md, so the only thing that's changed are pandoc-specific things, like adding a title page and table of contents.

Note that for the table of contents to render in md properly, we must use github-flavored-markdown.

[OleksiyPuzikov]

From the very quick overview, LGTM - thanks @pmolodo

I noticed the change in the expected Markdown requirements, I assume this was tested.

[pmolodo]

I noticed the change in the expected Markdown requirements, I assume this was tested.

I meant to mark this as DRAFT, as I'm working on a detailed comparison of what changes when switching to gfm. Short summary is that it DOES result in changes in html/pdf, but thus far it seems to be fairly minor / cosmetic stuff (ie, in html, “ characters are now replaced with ", insertion of <span> tags inside of some <a> tags...)

[pmolodo]

So, after realizing that our current combined_spec.md does not have a consistent markdown style (it's a mix of markdown (pandoc's own markdown variant) and gfm (github-flavored-markdown), and a few attempts to unify it for consistency, I opted for this current less-invasive change for now. It only sets the format of the final "output" aousd_core_spec.md to be gfm.

Will file a issue to make markdown more consistent, targeting post-1.1

[pmolodo]

New version doesn't change any previous outputs, but just adds a .md (with title page and TOC).

Removing draft, ready for review.