Fix broken link to API reference

The link to the API reference was pointing to api-ref-orchestration,
which is incorrect.  This changes it to api-ref-orchestration-v1.

Closes-Bug: #1320956
Change-Id: I3eb46af60dffc47e62ffbfc9f407f7f1a86a56a1
test_engine_service remove redundant DummyThreadGroups

Remove DummyThreadGroup assignments, since they are assigning to an
EngineService attribute which no longer exists (it's a legacy from
an older heat-engine implementation)

Change-Id: I60de53e88eeb56ab36ec7f3a697fd856b1a84925
Unit tests: remove resolve_runtime_data() call

This was accidentally reintroduced after a merge conflict.

Change-Id: Ibae58aae1520d8f934b59eb9dae6979d95a0a312
Allow functions to calculate dependencies

Change-Id: Ic58f54612d3707abc8727a65a28b9c4502eae31a
Remove unnecessary coding line

As per PEP 263, a Python file with non-ASCII characters must have a
line with "coding: <some-encoding>". This file is pure ASCII, so the
line is unnecessary.

Change-Id: I73d07bc0d80ac4dab484bf2a311818a5f6489dc0
Use Emacs-friendly file variable to set file encoding

The file encoding line serves a dual purpose: it informs both Python
and Emacs about the file encoding.

PEP 263 explains that a file with non-ASCII characters must specify an
encoding. Without an encoding line, importing the file will raise a
SyntaxError.

The problem is now that while Python will accept both of

  -*- encoding: <some-encoding> -*-
  -*- coding: <some-encoding> -*-

and Emacs only accepts the latter since it looks for a file variable
named "coding", not "encoding". Since the Emacs specific "-*-" syntax
is already used, it seems right to use the correct variable for Emacs.

Change-Id: If5321ac2fad595c529aa3ec5f2852aa71458834b
Merge "Fix broken link to API reference"
all non debug log messages should be translated

Updated a set of files to add missing translation support in the
log messages.

Change-Id: I58d561c5e1ecff550483ee0be696999e927c98ad
Partial-Bug: #1321283
Merge "Use Emacs-friendly file variable to set file encoding"
Implement context manager for stack lock

This is to give the engine service methods a means to use the stack lock
that guarantees it will be released if there is an exception.

Change-Id: I6d0e1e7c22f4e74eeb069f980bc09a14f3740beb
Partial-Bug: #1321011
Use stack lock context manager in abandon & delete

This will ensure that the stack lock is always released when there is an
exception.

Change-Id: I6d65c57d8b92107eb84c5ed1fbfd5eca30bace01
Partial-Bug: #1321011
Remove support for nova volumes

Note this is only supported if for some reason cinder client
is not imported, which seems rather random.

Change-Id: Id57ba93ef8202ba2a513ee21aff02e4dac9ec21e
Merge "all non debug log messages should be translated"
Merge "Unit tests: remove resolve_runtime_data() call"
Merge "Allow functions to calculate dependencies"
Merge "Implement context manager for stack lock"
Merge "Use stack lock context manager in abandon & delete"
Merge "Remove unnecessary coding line"
Merge "Remove support for nova volumes"
Merge "test_engine_service remove redundant DummyThreadGroups"