Add @@PLUGINSTART-USE-STRICT@@ Replacement

[hayeswise]

Add support for new replacement, @@PLUGINSTART-USE-STRICT@@. The replacement is the standard PLUGINSTART code followed by "use strict";.

For plugin example that uses this:

• Easy Button Demo - source
• Easy Button Demo - build
• Or load it directly with Tampermonkey/Greasemonkey: Easy Button Demo plugin

---

Following has been removed per guidance from nhamer to keep the changes focused on one item:

Also add a --verbose option to show which files are being built.
Sample verbose option output during the build:

> python build.py local --version
Buidling total-conversion-build.user.js
Buidling plugins\add-kml.user.js
Buidling plugins\ap-list.user.js
...

[nhamer]

Uh, there's a lot more changes here than should be necessary for the patch. It should just need the pluginWrapperUseStrict (which, really, should be X + usecommon) and then the alternate macro.

[hayeswise]

Okay, I can back out the verbose option easy enough. And make the other requested change. A pluginWrapperUseStrict = pluginWrapperStart + "use strict;" approach will not work since the "use strict" needs to go immediately after the function wrapper(plugin_info) {. Now, I could split pluginWrapperStart into two parts/variables, say pluginWrapperStartOpening and pluginInWrapperStartClosing. Or, use a replacement string approach.

[nhamer]

I'd have pluginWrapperStartCommon = "most of it"; and then pluginWrapperStart and pluginWrapperStartStrict add the extra couple lines at the top

[hayeswise]

After considering the options, I went with the one line approach:

pluginWrapperStartUseStrict = pluginWrapperStart.replace("{\n", "{\n\"use strict\";\n", 1)

Also removed the --verbose feature.

[nhamer]

Erm, you just added a couple extra files.

[hayeswise]

Sorry, this is the first time I've done this with a repository that wasn't mine. I'll get to it. Thanks for keeping me on track.

[hayeswise]

I got this down to the one file and checked it via the "Files Changed" link, above.