Use @npm task (#1152)

* remove global config and test

* add sqlbindings to path

* test with sqltools feed

* remove globalconfig

* add globalConfig back

* undo .npmrc

Author: MaddyDev

builds/azure-pipelines/template-steps-build-test.yml

@@ -24,11 +24,19 @@ steps:
   inputs:
     workingFile: $(Build.SourcesDirectory)/.npmrc
 
-- script: npm install azure-functions-core-tools --global --globalconfig $(Build.SourcesDirectory)/.npmrc --loglevel verbose
+- task: Npm@1
   displayName: 'Install Azure Functions Core Tools'
+  inputs:
+    command: 'custom'
+    customCommand: 'install azure-functions-core-tools --global --globalconfig $(Build.SourcesDirectory)/.npmrc --loglevel verbose'
+    workingDir: '$(Build.SourcesDirectory)'
 
-- script: npm install azurite --global --globalconfig $(Build.SourcesDirectory)/.npmrc --loglevel verbose
+- task: Npm@1
   displayName: 'Install Azurite Local Storage Emulator'
+  inputs:
+    command: 'custom'
+    customCommand: 'install azurite --global --globalconfig $(Build.SourcesDirectory)/.npmrc --loglevel verbose'
+    workingDir: '$(Build.SourcesDirectory)'
 
 # This step is necessary because npm installs to a non-traditional location on Windows hosted agents
 # For non-Windows agents we still want to ensure that we always get the correct location where the tools are installed