Updated from global requirements

Change-Id: I285fd19a324620ef45551d3844719d7c39767f9e
Stub out unmocked keystone auth in signal tests

While these tests do setup a mock for keystoneclient, one of the tests
clears out these stubs before exitting to avoid needing to stub out
things stack_delete_after will do. However, stack_delete_after will
trigger a call to keystoneclient which leads to unmocked calls trying to
reach server.test from inside the tests. These failures go undetected
because they are after the test, and nothing is checking for error
events in this phase.

Change-Id: I608e0b5a263587d5151b4cb4ce3f03e289c4bdca
Partial-Bug: #1227962
use msg_fmt not message in Exceptions

This doesn't solve the problem yet, but clarifies
the format string from the final string.

Partial-bug: #1243883
Change-Id: Ia0f19423248304984cc53926dfb87c6a49c90e11
Fix nested stack test setUp ordering

This fixes an irrating message during test runs:
No handlers could be found for logger "heat.engine.environment"

This was because the environment was loading before the fake logger
was enabled.

Change-Id: I1a40998fe37bf29529ef2eae348c6918bf56966b
Merge "Updated from global requirements"
Merge "Fix nested stack test setUp ordering"
Merge "Stub out unmocked keystone auth in signal tests"