Use wsgi.response for v2.1 unrescue API

According to the comment on v2.1 unrescue API, v2 unrescue API seems
to return a HTTP200 response on success case. However that is invalid
and it returns a HTTP202 response like the following:

 $ curl -i 'http://nova-api/v2/{tenant-id}/servers/{server-id}/action'
   -X POST -H "Accept: application/json" [..] -d '{"unrescue": null}'
 [..]
 RESP: [202] CaseInsensitiveDict({'date': 'Tue, 21 Oct 2014 02:23:42 GMT',
   'content-length': '0', 'content-type': 'text/html; charset=UTF-8',
   'x-compute-request-id': 'req-642b49e8-0e13-4923-a49b-6c8b317b7b8c'})
 RESP BODY: null

This patch removes the comment and makes the API use wsgi.response for
the code cleanup.

Partially implements blueprint v2-on-v3-api

Change-Id: Ie78e56fafd71f58568a0562b9a452f14d3b19815
Separate NUMA topology filter unit tests

Breaks out the NUMA topology filter unit tests from test_host_filters.py
into its own test file.

Change-Id: Icd52c923bfb81836c9b346dff5175bb4d6fac037
Separate isolated hosts filter unit tests

Breaks out the isolated hosts filter unit tests from
test_host_filters.py into their own test file.

Change-Id: I9b64638172e8d5e527c9d29548e3f5ba0d3d17e1
Merge "Separate NUMA topology filter unit tests"
Merge "Separate isolated hosts filter unit tests"
Merge "Use wsgi.response for v2.1 unrescue API"