Setup a testing environment and better sample setup.

This doesn't actually change anything in the library - but it changes the repos folder structure and project setup for the better and adds a test environment (which I will flesh out on Friday with some integration and unit tests with KIF and SenTest) 
If you're not sure, please pull down my fork and run the workspace and check out the folder structure.
Read more...

1) Added an testing environment to write tests easier.

2) Added guard files for continues testing (requires ruby)

3) Sample project now uses Cocoapods

4) CZPhotoPickerController library is now used via a local pod in the workspace on the sample target

5) The test target is dependent on the sample target and the pod adds some test libraries to help out.

6) Will use sample project for Test Host for integration tests

7) Added two shared schemes, Sample and Tests (this is later so Travis-CI can run them)



This all sounds complicated but is actually kinda easy. When you want to add some changes just open up the work space and do your changes in the local pod. It will directly change the files themselves as they are symlinked into your project. Makes it easier to do changes in the library and sample at one place.

I also added tests with a test host app (the test host app is the sample app) with a shared scheme that will run by Travis.

I have some features to add to CZPhotoPickerController, but in order to do that, I'd rather write some tests first, but in order to write some tests first I need to add an environment that would be easy to use with tests as well as editing code and samples at the same time.


 I intend to write tests and then later add some features that allows user to use the library with blocks but without using an action sheet   for apps that use custom UI for action sheets or whatever