[BUG] comment doesn't work when first field in line is escaped

[amitbeck]

Describe the bug
Seems that if a line, which is supposed to be a comment, starts with an escaped field (i.e. "# e.g. apples, oranges, grapes") - the line is not detected as a comment and is included in the output.
See reproduction on RunKit: https://runkit.com/embed/jhkygl35xji6

Parsing or Formatting?

• Formatting
• Parsing

To Reproduce
Steps to reproduce the behavior:

1. Example file contents if applicable

   header 1,header 2,header 3
   "# comment 1, which includes a comma",# comment 2,# comment 3
   value 1,value 2,value 3
   

   referred to in the next example as escapedCommentFieldCsvString
2. Example code to reproduce the issue
   Options passed to the parse method:

   {
       headers: true,
       comment: '#',
       trim: true,
       strictColumnHandling: true,
       ignoreEmpty: true
   }

3. Output:

   { "header 1": "# comment 1, which includes a comma", "header 2": "comment 2", "header 3": "comment 3" }
   { "header 1": "value 1", "header 2": "value 2", "header 3": "value 3" }

Expected behavior
Output should not include comment lines whose first field includes comment token but is escaped.
The expected output is:

{ "header 1": "value 1", "header 2": "value 2", "header 3": "value 3" }

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: MacOS
• OS Version: Big Sur 11.6.4
• Node Version: v16.13.1

Additional context
@fast-csv/parse version 4.3.6