Named parameter is not recognized for blob trigger if the Container name in function.json does not match the container name in Run Now

Named parameter is not recognized for blob trigger if the Container name in function.json does not match the container name in Run Now. This is not an issue if the function.json does not have a named parameter.

Please provide a succinct description of the issue.

Steps
1) Create a Function using Blob-Trigger NodeJS template
1) Use the following as path property in function.json
`path: images/{name}`

2) Use the following in the run now text box
`sample/image.jpg`

**Expected Output:**

```
Node.js blob trigger function processed
Blob: image.jpg
Blob Size: 40286 Bytes
```

**Actual Output:**

```
Node.js blob trigger function processed
Blob: undefined
Blob Size: 40286 Bytes
```

For C# this results into an exception
`Exception while executing function: Functions.BlobTriggerCSharp1. Microsoft.Azure.WebJobs.Host: Exception binding parameter 'name'. Microsoft.Azure.WebJobs.Host: Binding data does not contain expected value 'name'.`

Reproduce the blob-trigger case using function.json with path images/{name} and Run Now input sample/image.jpg, starting with the binding behavior shown by the Node.js template and the C# exception. The fix is done when the named parameter receives image.jpg despite the differing container names, with the documented expected output preserved.

Written by the indexing model from the issue text.