Use mox for mocking quantum client test calls

There is no change in test coverage, future commits will
expand the code coverage on quantum resource types

Change-Id: I90cb1a2d1073d95c75b941b00b9c667a8c7a72d9
Initialise resources when service is created.

Without this, calls to validate_template will fail until the first
parser.Stack is created.

resources.initialise() is called in EngineService __init__
to avoid this happening in another service method in the future
Fixes: bug #1181045

Change-Id: I68a74ec7993aff4b74d449a3ae33315b93e9cb0d
Fix error in Dependencies representation

This mostly only exists for debugging, but it's helpful if it can actually
run.

Change-Id: Ie29da5e7e58aed54aaaffa4df479fa0d96ce78fe
Align usage of test skipping.

There were three different mechanisms for skipping tests in the suite.
For the most part, skipIf was used, so sync to that. Additionally, it
was being used as a decorater in most places, but as a call in a few,
so make it a decorator everywhere. Finally, if it's on the setUp method,
it's not necessary for it to be on any of the individual tests in the class.

Change-Id: I7fbd09a6bc015e698a190b989d0f8641c4adb63e
Clean up a pyflakes error in a comment.

This is a little-bit silly, but it's the last thing. pyflakes parses
python lines that are in docstring comments that are prefaced by >>>.
So, without the import, pyflakes complains about undefined import.

Change-Id: Ibac77367efb07b65b992694b2de19473ec9ef473
Merge "Initialise resources when service is created."
Merge "Fix error in Dependencies representation"
Merge "Use mox for mocking quantum client test calls"
Merge "Align usage of test skipping."
Merge "Clean up a pyflakes error in a comment."