Use DigitalOcean token instead of api user/key

Related to #886 - I tried to run `vagrant up` on my machine using a DigitalOcean configuration, and it kept giving me the error:

```
Digital Ocean Provider:
* Token is required
```

Since I already updated the `config.yml` with my token, I was very confused. Changing these lines in the Vagrantfile to use the token instead of the client_id and api_key resolves this issue.
Merge pull request #933 from vlucas/patch-1

Use DigitalOcean token instead of api user/key
Enables php-fpm; removes mod_php; forces fcgid
Checks if apt class predefined. Fixes #935
Merge branch 'master' of github.com:puphpet/puphpet
Explicitly includes puphpet::params for all extensions. Fixes #937
General cleanup
Slight visual change for chaining
Moves supervisord and composer into puphpet module
Moves handling php repos into puphpet module
Composer is in puphpet module
General cleanup
Allows passing port to fcgi config
Allows passing port to fcgi config for nginx
Missed a }
General cleanup; Adds puphpet::params
Sets up mod_php selection
Merging master into apache-php-fpm
Slight readibility changes
Adds defined check out apt::key. Fixes #943