Blob Trigger Throw OutOfMemoryException

#### Description of Issue and steps to reproduce
Using default Blobtrigger type Azure Functions App:
1. Using a large file: 100Mb
1.1. Start debug in VS Code
1.2. Add file to Azure blob storage container
1.3. Blobtrigger app throws an OutOfMemoryException.

2. Using a small file: 1Kb
2.1. Start debug session in VS Code
2.2. Add file to Azure blob storage container
2.3. Blobtrigger app triggers and succeeds

#### Workaround
Using default HTTPTrigger type Azure Function App:
SETUP
1. Add Blob type input binding
2. Set `"path": "/{query.filename}"`
3. Create an MS Flow which triggers when blob is added to the blob storage.
4. Add an HTTP request action
5. Pass the filename from the blob trigger action to the HTTP request action

USE
1. Add file to Azure blob storage container.
2. MS Flow will trigger
3. MS Flow will initiate an HTTP request with filename as parameter
4. HTTPTrigger App receives the request and uses the filename during runtime to configure the blob storage
5. HTTPTrigger App read all the data from the blob using: `InputBlob.read()`

NOTE:
When manually initiating an HTTP request, with filename of file in blob storage, the Function App also succeeds and provides access to the content of the blob via the `InputBlob.read()` method.

Start by reproducing the Azure Blob trigger in VS Code with the reported 100 MB and 1 KB files, then compare the OutOfMemoryException with the successful HTTP trigger workaround. The issue is resolved when the Blob trigger can process the large file without exhausting memory, with the existing reproduction steps used for verification.

Written by the indexing model from the issue text.