DP: Improve SteemD required resources for API recipe

[relativityboy]

As a person setting up a SteemD node for the first time, I want someone to hand-hold me through my first configuration so that I can have an easy and pain free experience running my first SteemD node with all the apis I want running perfectly out of the box.

Supporting Materials

• DP: Answer the question: When enabling which SteemD plugins require a chain replay steem#2909 (part of the gotchas section)

AC

• the file from Community - Document Steem plugins #269 is enhanced with detailed information about where to put configuration resources to enable the apis, including special breakouts for 'extra special configs' and 'gotchas' that may be needed. (incl specific OS & version)
• instructions for machine conforming to AWS environment, incl link to setting up said environment.
• covers both docker & raw builds

[relativityboy]

Expl not just that you should use Ubuntu, but why. Even incl as block quote

[relativityboy]

Looked at pointing story. Came back with needs for creating good tutorial

• easy boot aws instances for testing different combinations
• solid understanding of implications of launching different plugins on shared-memory file contents (which ones need different shared memory file contents)

[relativityboy]

Blocked by above needs.

Consider aws automation with Chef to get to easy boot aws instances for testing different combinations . Wondering if @jredbeard has thoughts about that.

steemit/steem#2909, when complete will address primary blocker