Fix order of arguments in assertEqual

Some tests used incorrect order assertEqual(observed, expected).

The correct order expected by testtools is
assertEqual(expected, observed).

Change-Id: I1184cb9f163ffb6416be32ddb1386c3bfd9b1006
Closes-Bug: #1259292
Configure logging regardless of debug flag

Configure the logging level for the client. Default to ERROR
unless -d is passed, then use DEBUG.

Closes-Bug: #1273800
Change-Id: Iea337bed55ca7da2fc95d0d3218a4895909423cd
Populate files with content from get_file function calls

This is the client-side implementation of the get_file HOT
intrinsic function. The data for each resource is recursively
crawled to look for {get_file: <path>} calls. The content for
the URL specified by get_file is fetched and the content stored
in the files field in the API request.

If a relative path is specified, that path is converted to an
absolute URL, and that URL is used as the key for the files
content entry. The template is also modified to replace the
relative path with the absolute URL.

This implements the client-side portion of
blueprint get-file

Change-Id: If1da98578bb2919e3c8325442224376d3fadb0bc
Merge "Configure logging regardless of debug flag"
Merge "Populate files with content from get_file function calls"
Add pagination (limit and marker) to stack-list

Add support for ``limit`` and ``marker`` on stack-list and remove
unnecessary ``page_size`` parameter.

When using ``limit`` and/or ``marker``, stack-list will keep previous
behavior and list all stacks starting from ``marker`` up to ``limit``,
even if limit exceeds API limit restrictions, by using multiple calls
to /stacks endpoint.

Partial-Bug: 1268816
Change-Id: Ifb08c1aadd3629d60ddc56ffc507c99b9dba80ce
Add filter option to stack-list

Add ability to use filters on stack-list by passing a ``--filters``
options to the command line.  This option can appear multiple times or
be used once with several key=value filters separated by semicolons.  If
the same key appears more than once, both will be taken into account
when sending the request to the API.

e.g.:
The option:
``--filters status=COMPLETE;status=FAILED``
Will issue the call:
 ``/stacks?status=COMPLETE&status=FAILED``

Closes-Bug: 1268816
Change-Id: I553d6b5e3ceebdb24dcd4e4c8e409a4375d72333