Remove skip for the CLI content views testcase

The bug is verified and also by having the decorator was causing the bug
reported on #936
Remove skip for the CLI subscription testcase

The bug is verified and also by having the decorator was causing the bug
reported on #936
Update bz bug to skip CLI content host test
Improve CLI OS test_bugzilla_1051557
Remove skip for the CLI template testcase

The bug is verified and also by having the decorator was causing the bug
reported on #936
Update CLI activation key update tests
Update CLI Organization test_add_user
Skip CLI org tests due to description update bug
Merge pull request #937 from elyezer/cli-tests-fixes

Cli tests fixes
Add method `get_server_credentials`

New method simply returns a tuple of ('username', 'password'). It's simple, but
more convenient than reading values from the config incrementally. Also, add
unit tests for the new method.
Create some simple tests for path api/v2/hosts

Implement a few tests which check whether it's possible to GET or POST to the
path. Check for things like whether an HTTP 200 is generated when a GET request
is issued, that sane sets of data are returned, and that an HTTP 401 is
generated when an unauthorized HTTP request is made.
Decorate method with `skip_if_bz_bug_open`
Create some simple tests for path api/v2/models

Implement a few tests which check whether it's possible to GET or POST to the
path. Check for things like whether an HTTP 200 is generated when a GET request
is issued, that sane sets of data are returned, and that an HTTP 401 is
generated when an unauthorized HTTP request is made.
Make Testimony happy with docstrings
Refactor tests

Use a `for` loop instead of repetitively listing out function calls.
Further refactor tests

Add fauxfactory to `requirements.txt`. Use fauxfactory in the tests.
Further refactor tests

Use random strings instead of hard-coded strings. Improve error message
handling.
Change expected HTTP status codes to 201

The HTTP 201 status code means that a resource was created. The tests which
attempt to create a resource should expect an HTTP 201, not an HTTP 200.