custom DictMatches matcher in unit tests can be removed

[Pavlo Shchelokovskyy]

Ironic only supports py27, and on py27 the assertEqual handles nested dicts comparison just fine

if one does not use the assertEqual (that is overriden from unittest[2] by testtools) but assertDictEqual (coming from parent classes directly), you even get a nice output highlighting where is the difference between dicts

this custom matcher is used in only one test module, and assertDictEqual handles those cases currently using DictMatches just fine.

[Ruby Loo (rloo)]

Although not officially, ironic will need to support py3.4 too.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/224287
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=9670d2bd26a6228f6150f4698b2c55b4348af395
Submitter: Jenkins
Branch: master

commit 9670d2bd26a6228f6150f4698b2c55b4348af395
Author: Pavlo Shchelokovskyy <email address hidden>
Date: Wed Sep 16 22:58:04 2015 +0300

    Remove DictMatches custom matcher from unit tests

    On Py27 assertDictEqual handles nested dictionaries just fine.

    Change-Id: I0695a1249a3c4153ba4cc49405640a3e09a2af04
    Closes-Bug: #1496552