Migrate transcripts to markdown file instead of stored in YML

[bencodezen]

Summary

This should make it easier for us to manage from a file perspective and any time people identify issues with the transcript it should be easier to issue a PR.

Concept

The perfect transcript file would have a snippet like the following:

[00:00] Ben Hong: Welcome to Enjoy the Vue. 
[00:10] Elizabeth: Hello!
[00:20] Chris: And here is my Twitter handle: [@gloomylumi](https://www.twitter.com/gloomylumi)

What would be great is if we create a custom renderer to interpret the following:

1. Timestamp: It would change the timestamp (i.e., [0:00]) into a link that users can click where it would skip them to the appropriate section of the audio clip
2. Name: Each panelist / guest could be linked to their appropriate page upon configuration. So I'm thinking we need to provide the renderer with a config file for each person's bio page.
3. Render everything else as normal markdown

Let me know what you think!

[znck]

We are using marked to process markdown at runtime. Should we move that to compile-time (so we can use remark and plugins)?

And what do you think about creating a separate transcript file using WebVTT?

[bencodezen]

@znck In the past we've used Rev.com and they've given us files like the following:
GMT20200130-185755_Enjoy-The-.txt

[bencodezen]

So just to be clear, we would have a transcript already generated at this point. You don't have to worry about audio transcription. We just need to be able to ingest the file and render out the correct blocks.