1. In case of federated vCenter [vCenter along with some other orchestration model]
i. /vcenter/login does authentication via vcenter auth plugin
   /login does authenitcation via the other orchestration model specified in config file
ii. Default landing page is "Monitor > Networks"

2. In case of only vCenter orchestration
i.  /vcenter/login does authentication via vcenter auth plugin
    /login redirects to /vcenter/login
ii. Default landing page is "Monitor > Infrastructure"

3. If logged-in via vCenter URL
    a. All URLs show "vcenter" in URL like "https://<ipAddress>:<port>/vcenter/#.."
    b. Clicking on Logout takes to vcenter login page
    c. Redirect to login page when vcenter SOAP session expires
    d. Display only vcenter projects

Infra Changes:
1. Added SOAP interface to communicate with SOAP servers
2. Store the current logged-in orchestration mode in request session object [req.session.loggedInOrchestrationMode] and the same is available via webServerInfo on UI side.

Config File Changes:
1. Option to specify custom wsdl file path for vcenter
    If this path is not found,it picks up the file from "webroot/js/vim.wsdl"
2. Multiple orchestration models can be specified via comma seperated in config file

vCenter specific configuration changes:
1. Added wrapper functions for interacting with vCenter SOAP server like [createIpPool,createDataCenter,...]

Change-Id: I281504e21782398ed92eee93c3333c1d84bab676
Filtering the VCenter projects,networks,instances fromt the API server and displaying in corresponding pages of network monitoring,in case if the orchestration model is VCenter

Change-Id: I3c2c751393de16b87a94e2c5e20979f757c15b3a