Fix issues #1, #3

[madhurig]

• Allow task to work in build and release definitions
• Allow specifying a one-time passcode for single sign on workflows
• Update extension build process
  

[sbachuMSOL]

Honestly speaking sso passcode option may not work in the CI process, because it requires updating the build or release definition before every the trigger - unless the tool can get the onetime passcode. FYI: based on the Cloud Foundry provider one time passcode may not valid for certain days.
Our configuration with Cloud Foundry is integrated with active directory "SAML token authentication". We created a custom Powershell script that can make webrequest calls to get the onetime passcode and inject it into the cf calls.

[madhurig]

@sbachuMSOL: I agree the one-time passcode will not be as straightforward to use in the CI scenario. But with the change I made, the one-time passcode can be specified by a build variable. So if you have a custom script that gets the one-time passcode, you can set the variable at the end of the script and the Cloud Foundry task will pick up the passcode.

We will consider providing another task that makes it possible to acquire the password for some common integrations.

Thanks,
Madhuri