HOLD: Adding robo - redo after https://github.com/United-Philanthropy-Forum/km-starter-kit/pull/25

[mariacha]

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 adding-robo with the name of this branch, and robotest with an example project name.

What this PR does:

• [ ] Adds robo. It's an older version because we're locked at drush 8x, but it still works.

How to test this branch:

• [ ] If you haven't already, run the One time setup steps
• [ ] 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-adding-robo" robotest

• [ ] Validate that a new site exists at https://dev-robotest.pantheonsite.io
• [ ] Validate the repo exists at https://github.com/United-Philanthropy-Forum/robotest
• [ ] Update your .env.dist to contain the robotest in the "TERMINUS_SITE" section. Make sure you can run a robo install from the dev environment.
• [ ] Delete the test environment when you're done, by running terminus build:env:obliterate robotest
• [ ] Once this PR is merged, cut a new tag so the create-project commands will get the latest and greatest.

TODOS:

• [ ] We'll want to document how to use robo install somewhere. Probably here: https://github.com/United-Philanthropy-Forum/km-collaborative/wiki/Local-development#pulling-down-pantheon-database

[unclegcb]

Okay I'm looking at this again and it's real old. We probably need to re-do this?

[mariacha]

Oh yeah, probably going to just drop this since Robo-drupal is handy for sites we work on but we don't want to impose it on other sites. Closing and dropping.