Scenario manager: catch Exception in get_remote_client

Several scenarios have the same try/catch block around get_remote_client,
let's factor this.

Change-Id: Ib22624236503c2ee7665af006a4976fe4b127705
Firewall as a service API Test Enhancement

 Add Test to insert and remove firewall rule to firewall policy
    -Create a firewall rule
    -Create a firewall policy
    -Insert a firewall rule to policy
    -Validate the insertion of rule to policy
    -Create another firewall rule
    -Insert the another rule after the first rule
    -Validate the postion after the rule insertion after the first rule
    -Remove the rule inserted second time
    -Again Insert that  rule before the first rule
    -Validate the position of rule inserted before  the first rule

    Add Test audited attributes of firewall policy
    -Create a firewall policy
    -Validate the default audited attribute
    -Update the audited attribute to true
    -Insert a firewall rule
    -Validate the audited attributes of the firewall
     policy

Change-Id: Ib3fefb42b976e2ebb6921cab4290e9c7dbaa58c2
Basic networks Scenario Test Enhancements

Add test to update router admin_state_up attribute of the router
-Update admin_state_up attribute of router to False and check public
 connectivity
-Update admin_state_up attribute of router back to True and check public
 connectivity again

Change-Id: I3fd56c44411ff6919e15dd1033f6c13e58271f4b
Test to create bulk port

Add test to create bulk port for two different network
  -Create two different networks
  -Create a network_list
  -Call a bulk port function to create a ports
  -Verify the port network_id with the network id used
  -Verify the admin_state_up of the port

Change-Id: I39e3df635f24bbe0f288bb6ccf1300ee5132725e
Add more verbose info for wait_for_..._status methods

If this method failed because the resource will not reach desired
status, you just know expected status, not actual status at time of
timeout. It can help with debugging.

Change-Id: I583f0739bf771dd587acd13c1453ae6a440a9e87
Ensure extension aliases are used for nova based services

This commit fixes the extension checker in verify-tempest-config to
ensure that nova and nova based services are using the extension
aliases instead of the extension names. The extension names are meant
to be human readable and are not the best way to identify it. This is
what the tempest code is also expecting, however in some cases the
name was still being used by the verify tool, which was incorrect. As
part of this it was necessary to fix several other places where name
was being used instead of alias, or other extension list formatting
response checking was incorrect.

Change-Id: I35f5db655f065f29760515a26db1fb508d229393
Merge "Scenario manager: catch Exception in get_remote_client"
Merge "Firewall as a service API Test Enhancement"
Merge "Add more verbose info for wait_for_..._status methods"
Merge "Basic networks Scenario Test Enhancements"
Merge "Ensure extension aliases are used for nova based services"
Temporarily disable service-type test

With the advanced services disabled this test fails. In order to make
forward progress on the services split this test needs to be disabled
to allow the services split to move forward.

Related-Bug: #1400370

Change-Id: Ide264a371215bb6a56e52faab18296fb0cf0a74b
Merge "Temporarily disable service-type test"
Merge "Test to create bulk port"
fix to support multiple networks
Merge branch 'master' of https://github.com/JioCloud/tempest