docs: Refresh Init READMEs

[jfuss]

Issue #, if available:
N/A

Description of changes:
Refresh the READMEs. I wanted to get feedback on the NodeJS one before going further with others.

Main changes:

• Format/restructure
• Added notes about using the AWS Toolkit as another option for running/test/debugging within an IDE instead of the command line.
• More detail in areas about using CFN and SAM in a single template, moving event.json into an events folder, more descriptive instructions for different command (build/package/deploy).

Checklist:

• Write Design Document (Do I need to write a design document?)
• Write unit tests
• Write/update functional tests
• Write/update integration tests
• make pr passes
• Write documentation

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[sanathkr]

why is the prompt prefixed with "my-application"?

[sriram-mv]

Maybe {{ cookiecutter.project_name }} might be better, but we dont know the full path on the client system.

[sriram-mv]

But love the explicit instruction to create the S3 Bucket!

[jfuss]

Because I was going off of a more generic version of this and missed this when updating. Will update it with {{ cookiecutter.project_name }}

[sriram-mv]

Nice refresh on the docs! 🔥

[sriram-mv]

Maybe {{ cookiecutter.project_name }} might be better, but we dont know the full path on the client system.

[sriram-mv]

But love the explicit instruction to create the S3 Bucket!

[sriram-mv]

fetch logs generated by your "deployed" Lambda function? Does that make sense?

[jfuss]

Sure. I think that addition makes sense.

[sriram-mv]

Does mentioning some specific SAR apps also make sense? helps the user to continue the journey to more complex apps.

[jfuss]

Rebased with HEAD of develop, so appveyor should now pass.

[jfuss]

I would like to get the Node Readme updated first. Once this one is completed, I will translate this into all the other init (except depreciated runtimes that we need to remove).