fix: avoid conflict with double quote within data

[aleen42]

This PR contains:

• bugfix
• feature
• refactor
• tests
• documentation
• metadata

Breaking Changes?

• yes
• no

If yes, please describe the breakage.

Please Describe Your Changes

Strictly define what a stating quote is except for the case like that:

a,b"d

[jcapcik]

I was also looking for a way to account for quotes within an unquoted field, which some other parsers seem to handle just fine (Excel and Rainbow CSV being a few).

This change breaks stuff in a lot of situations though. However, it lead me to a slight change that seems to work at least in my current set of tests.

Instead of checking if i === 1, which is not correct since i is the zero-based index of the character in the entire file, not each line, check if i === start, which would indicate the start of the line:

const isStartingQuote = !isQuoted && buffer[i] === quote && (i === start || buffer[i - 1] === comma)

So we only consider a quote a starting quote if we aren't within quotes already, and it either is the first character of the line or it follows a comma.