Remove update_service_capabilities from nova

From the comments of update_service_capabilities, it is said that
once publish_service_capabilities was removed, then we can begin the
process of its removal.

publish_service_capabilities has been removed in patch
I31c21055163e94b712d337568b16b9b7a224b52f, so we can remove
update_service_capabilities now.

Change-Id: I46be33462321f5e3ff0904bdff8dbfe2fbe115cd
Closes-Bug: #1263569
Update class/function name for test_extended_availability_zone.py

In test_extended_availability_zone.py, it was using class name and
function name as following:
1) ExtendedServerAttributesTest
2) assertServerAttributes

This is not accurate as this test file is for availability zone,
this patch was change the above two names to:
1) ExtendedAvailabilityZoneTest
2) assertAvailabilityZone

Change-Id: I52d6ebcb1388fc10ac92d66cae166391d46e68c1
Allow _check_instance_build_time to hit db slave

If your deployment has a slave configured, _check_instance_build_time
will read against the db slave. If you have no slave configured
then behavior remains unchanged.

Change-Id: I2e19bef2b4231a711f473807a14a13398cbc7278
Partially-implements: blueprint periodic-tasks-to-db-slave
disk/api.py: resize2fs fails silently + adds tests

+ The method disk.api.resize2fs fails silently and should
  writes some information in the log.
+ Adds missing tests to disk.api.resize2fs

Change-Id: I4edd88fb85a73c75628958e3f2ea668c0d3cad89
Closes-Bug: #1270088
Merge "disk/api.py: resize2fs fails silently + adds tests"
support stevedore >= 0.14

the previous mocks made some very specific assumptions about the
behavior of an internal private method in stevedore, which changed
in 0.14. Make the mocks more flexible so they work regardless.

Change-Id: I5063c652c705fd512f90ff3897a4c590f7ba7c02
Merge "Remove update_service_capabilities from nova"
Merge "Update class/function name for test_extended_availability_zone.py"
Merge "Allow _check_instance_build_time to hit db slave"
Merge "support stevedore >= 0.14"