strict: false - headers lost after row with wrong number of columns

Nobody has claimed this yet.

* Operating System: MacOS 10.14.6
* Node Version: v12.11.1
* NPM Version: 6.11.3
* csv-parser Version: 2.3.1

### Expected Behavior

headers created with "mapHeaders" should be used for all valid records, even for records with to many or to less columns

### Actual Behavior

* when a line contains more columns than headers the broken record is returned with indexed keys.
* any valid line following the broken line is returned with indexed key and not with the headers

### How Do We Reproduce?
https://github.com/aheissenberger/csv-parser?organization=aheissenberger&organization=aheissenberger

```
1 test failed

strictNo › strictNo

/Users/ah/SVN-Checkouts/DEV/csv-parser/test/strictNo.test.js:9

8: const headersLastLine = Object.keys(lines[2])
9: t.deepEqual(headersFirstLine, headersLastLine)
10: t.false(err, 'no err')

Difference:

[
- 'a',
+ '0',
- 'b',
+ '1',
- 'c',
+ '2',
]
```

Start with test/strictNo.test.js and reproduce the failing assertion for the record after a row with too many columns. Trace the parser behavior that follows the malformed row; done means strict:false preserves the mapHeaders keys for subsequent valid records without producing an error.

Written by the indexing model from the issue text.