Pulling in changes from #92. Removing ScriptHandler, which can be who…

[mariacha]

…ley managed by Pantheon now.

For the PR creator:

Check off the following boxes before asking someone to review this PR.

• [x] If this PR changes the composer.json file, is there accompanying text in the README.md file explaining that change?
• [x] Update the "How to test this branch" instructions below by replacing issue-92 with the name of this branch, and test-92b with an example project name.

What this PR does:

• [x] For #12 Allows us to have a consistent RC branch during development.

How to test this branch:

• [x] If you haven't already, run the One time setup steps
• [x] Run this:

COMPOSER_MEMORY_LIMIT=-1 terminus build:project:create --team='United Philanthropy Forum' --org='United-Philanthropy-Forum' --visibility='private' --stability=dev "united-philanthropy-forum/km-starter-kit:dev-issue-92" test-92b

• [x] Validate that a new site exists at https://dev-test-92b.pantheonsite.io
• [x] Validate the repo exists at https://github.com/United-Philanthropy-Forum/test-92b
• [x] Validate you can make a persistent rc-1 branch.
• [x] Validate you can make PRs against the rc-1 branch and get the correct database and VR tests.
• [x] Delete the test environment when you're done, by running terminus build:env:obliterate test-92b
• [x] Once this PR is merged, cut a new tag so the create-project commands will get the latest and greatest.

[mariacha]

I had to run composer install once to get this to work. I think adding the circle and .ci files to the post-create-project-cmd will solve that problem.