ADO Extension should support nested directories for outputDir

[JGibson2019]

Describe the bug

If users pass a nested directory (e.g. "$(DefaultDirectoryPath)\parent\child')" to outputDir, and the parent directory doesn't exist yet, the extension should be able to create the parent directory and not throw an exception. Currently, the extension expects to be sent single layer/non-nested throws an error when expected to write to a parent directory that does not already exist.

To Reproduce
Steps to reproduce the behavior:

1. Navigate to the yaml file
2. Go to inputs
3. Go to outputDir and specify '$(DefaultDirectoryPath)\parent\child'
4. Try to build and receive the error "##[error][Exception]ErrorWithCause: An error occurred while scanning website page: undefined

CodePen repro example

Expected behavior

The extension should create the listed parent directory if it does not already exist.

Screenshots

Context (please complete the following information)

• OS Name & Version:
• Azure DevOps Extension Version & Environment:
• Browser Version:
• Target Page:

Are you willing to submit a PR?

Yes

Did you search for similar existing issues?

Yes

Additional context

This issue was brought to our attention on 3/27 through the support alias