[WIP] Orchestration

**Important note:** This pull request is a work in progress (WIP). Please do **not** merge it until "[WIP]" is removed from the PR title.

The intent of this WIP PR is to solicit feedback on the PHP API of Orchestration early and often.

The first set of commits to this PR will be non-functional code samples for Orchestration. The goal of this exercise to design the Orchestration PHP API from the perspective of a developer using this API. Please review these commits as they come in and provide feedback. This will ensure that the feedback is incorporated into future commits.

Once the PHP API is finalized via code samples, the next set of commits to follow will be documentation of the API. Specifically, these will be a Getting Started Guide (similar to https://github.com/ycombinator/php-opencloud/blob/master/docs/userguide/ObjectStore/README.md) and a Complete User Guide (similar to https://github.com/ycombinator/php-opencloud/blob/master/docs/userguide/ObjectStore/USERGUIDE.md). There will be links from the latter to the previously-committed code samples.

Once the documentation commits have been reviewed and finalized, the final set of commits to this PR will be the tests and actual implementation of the API, that is the various classes under the `OpenCloud\Orchestration` namespace.

Once the tests and implementation have been reviewed and finalized, this PR will no longer be WIP. At this point, it may be merged.

To summarize:
* [ ] Code samples
* [ ] Documentation
* [ ] Tests and implementation

/cc @gecampbell @jamiehannaford 
[@jamiehannaford I did a rebase against working and a force push (never doing that again) so I lost our conversation about URI schemes. So I'm recreating it here]

> > So it seems there are multiple ways of validating the template: by local path or remote URI. Should we expect end-users to remember different array keys? Can we somehow allow just a string and treat it either as remote or local based on the URI scheme?

> We could use URI schemes but two questions come to mind:
> 
> 1. Would we restrict the user to certain URI schemes, specifically `http://`, `https://` and `file://`?
> 2. How would we handle in-memory contents, that is a template represented as a string?
>