Queue Trigger - Job Status Not Updating Consistently for Concurrent Messages on Failures

#### Investigative information

- Timestamp: 2017-11-28T07:48:11.633
- Function App version (1.0 or 2.0-beta): 1.0 and 2.0-beta
- Invocation ID: 29d6bd12-1f51-4831-9d60-548693804af1,
- Region: East US 2

#### Repro steps

Triggering multiple queue messages causes the invocation log to skip updating the job status when a failure occurs in each queue message. queuing a single message does not exhibit this behavior - seems to be a concurrency problem.

#### Expected behavior

When failures occur and there are concurrent trigger executions the job status should still reflect the proper state

#### Actual behavior

Job status is never updated and appears to run forever even though the logstream shows it completed. when `host.json` timeout is exceeded it's marked as not finished even though the log showed it errored. resources are blocked while the job appears to keep running

#### Related information

* Programming language used: nodejs 6.5 / nodejs 8.5. tried using both `context.done('error')` and promises - both have issues
* Bindings used: queue trigger input
* Message Queue shows the messages stuck in *processing* state - dequeued but never marked failed for retry or poison
* Service Plan: dedicated, Large 2 (4 CPU, 2 instances), Small 1 (1 CPU, 1 instance) => all exhibit issue

> 2017-11-28T07:48:11.633 Function completed (Failure, Id=29d6bd12-1f51-4831-9d60-548693804af1, Duration=45811ms)
2017-11-28T07:48:11.691 Executed 'Functions.MyFunction' (Failed, Id=29d6bd12-1f51-4831-9d60-548693804af1)