add research for google cloud api, and various strategies for getting mic input

[Michael-Overall]

Addresses #11 .

Purpose:

• Add information on the pros/cons of google's speech to text api, and describe what is involved in setting up an account to make this happen.

• Add a description of utilities that allow for pulling in mic audio from user's hardware via software and packages like SOX and arecord.

• microphone-input-packages.md also talks about the possibility of doing different builds or using different packages on different platforms, and the ability to detect (some) platforms with the help of the Node.js property: process.platform

[Michael-Overall]

To build off of previous work from @steaward in mic-testing, I was also looking at a stack overflow discussion on piping child process data back to the calling script.

This might get us closer to streaming audio instead of saving it to a file, then processing it.

We can also probably grab the text that was being spit back to the command line and try to pass it into the editor's window (see this article on putting text in the IDE

in extension.js:

        startMic.then(function () {
            spawn.exec('python ' + pyScriptLoc, {cwd: __dirname}, (error, stdout, stderr) => {
                console.log("going to gather the words...")
                if (error) {
                    console.error(`exec error: ${error}`);
                    return;
                }
//we may be able to grab the text in the 'stdout' variable and shove that into the editor
                console.log(`Words you spoke: ${stdout}`);
            });
        })

    });

I'll start a new issue in regards to this.