Ft24-2: Fix Errors in Local Integration Run on Windows

Purpose

A pre-requisite of the 4th criteria in #24 is the ability of the pipeline to run integration tests on a locally running function within the azure pipeline. This PR fixes previous issues that prevented this from running.

Does this introduce a breaking change?

[ ] Yes
[X] No

Pull Request Type

What kind of change does this Pull Request introduce?

[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

cd ./integration-tests
npm run local:test:windows

What to Check

Verify that the following are valid

Integration tests should successfully run in a job on the pipeline, with the following at the bottom of the log.
```
Function App stdout: Worker process started and initialized.
Function App stdout: 
```

Function App stdout: [2020-10-09T07:47:48.766] Listening for transport dt_socket at address: 5005

Function App stdout: Hosting environment: Production Content root path: D:\a\1\s\target\azure-functions\user-account-service-function

Function App stdout: Now listening on: http://0.0.0.0:7071 Application started. Press Ctrl+C to shut down.

..................................................................... Test is against a locally running function. Tearing down the function.

Terminating the functions process running with id 4072 Attempting to clean-up any other processes using the function port

24 scenarios (24 passed) 69 steps (69 passed) 0m05.689s



* Locally running the tests should yield a similar output

## Other Information
<!-- Add any other helpful information that may be needed here. -->

math-dojo / user-account-service