1. Added escape sequence support: Modified the header parsing logic…

[cbaugus]

… to handle escaped commas (,) in header values

2. Created a new parsing function: parse_headers_with_escapes() that properly handles the escape sequences
3. Added comprehensive tests: Created 7 test cases covering various scenarios including:
   - Simple headers without commas
   - Headers with escaped commas (like Keep-Alive)
   - Multiple escaped commas in a single value
   - Backslashes that aren't escape sequences
   - Edge cases with whitespace and trailing commas
4. Updated documentation: Added clear examples in the README showing how to use the escape sequence feature

The solution allows users to include commas in header values by escaping them with a backslash. For example:
-e CUSTOM_HEADERS="Connection:keep-alive,Keep-Alive:timeout=5\,max=200"

This will correctly parse as two headers:

• Connection: keep-alive
• Keep-Alive: timeout=5,max=200