Expected Behavior

As a driver user
I expect unordered bulk insert operations to consistently match operation results
When calling getSuccessfullyInsertedIds with interspersed op types

Actual Behavior and Impact

• When calling getSuccessfullyInsertedIds, it's possible for the insertedIds list to include indexes that refer to unrelated operations durig a bulkwrite.
      Expected behaviour: the correct operation index should be used 
• No customer reports

Dependencies

• None

Risks/Unknowns

• None

Acceptance Criteria

Implementation Requirements

• modify the insertedId's insertion items to include the proper index of the op

Testing Requirements

• Integration tests should be added to protect against the failure scenario in which getSuccessfullyInsertedIds can return invalid data after a partially-successful bulkWrite.

Documentation Requirements

• Release note crediting the user who submitted the fix

Follow Up Requirements

• A spec test should be added to cover that an unordered bulkwrite maintains affinity between op indexes and result indexes on insertedIDs when the bulkWrite has interspersed operations