Incorrect response for GET /v3/artifacts/type

[Alexander Tivelkov]

The call "List Artifacts" (both "drafts" and active ones) should return a regular pagination data structure (the dict with "artifacts", "next" and "first section), so it may be paginated in a regular way.
This does not happen: the list artifacts call returns just an array of artifacts.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/214600

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/214600
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=67d70009301f1200c193e346c91444f1960876d6
Submitter: Jenkins
Branch: master

commit 67d70009301f1200c193e346c91444f1960876d6
Author: Alexander Tivelkov <email address hidden>
Date: Wed Aug 19 15:57:28 2015 +0300

    Fixed the output of list artifacts API calls

    The output of list artifacts calls (GET /v3/artifacts/sometype and
    GET /v3/artifacts/sometype/drafts) contained just a json-array of
    artifacts, instead of a proper dict, containing "artifacts", "next" and
    "first" section.
    This patch fixes it.

    At the same time it fixes a minor bug in artifacts' SQL Alchemy API
    which prevented pagination queries from working properly when the marker
    was passed.

    APIImpact
    Closes-Bug: #1486118
    FastTrack

    Co-Authored-By: Alexander Tivelkov <email address hidden>
    Co-Authored-By: Kairat Kushaev <email address hidden>

    Change-Id: I46cce6654c2120aafe92bb885ab0c3453fe485f8