config: accept empty lines in double-quoted strings

[AkashKumar7902]

Which issue(s) this PR fixes:
Fixes #4691

What this PR does / why we need it:

Double-quoted configuration values previously handled a physical line ending together with its preceding character. When the parser was already positioned at a line ending—such as on an empty line or after an escaped literal backslash—it instead reported an unexpected end of file.

Handle backslash line continuations and preserved line endings explicitly. This accepts empty lines, preserves LF and CRLF, and retains the existing single-backslash continuation behavior.

Docs Changes:

None. The existing multiline-string documentation already describes the intended behavior.

Release Note:

config: accept empty lines in double-quoted strings.

Testing:

Automated:

• bundle exec rake test TEST=test/config/test_literal_parser.rb — 220 tests, 223 assertions, 0 failures, 0 errors
• TEST_ENV_NUMBER=focus4691 bundle exec rake test TEST=test/config/test_config_parser.rb — 56 tests, 106 assertions, 0 failures, 0 errors
• bundle exec rake test (two independent runs) — 4,343 tests, 15,829 and 15,830 assertions respectively; 0 failures, 0 errors, 3 pendings, and 36 omissions in both
• rubocop — 459 files inspected, no offenses
• ruby -c for all three changed Ruby files and git diff --check

Manual (Ruby 4.0.6):

• Built and separately installed gems from baseline f380d996bc828b5cd488b578018c06826ebcbf7e and candidate 7d017869a55e179da4d195806f26d33dc485fc9d.
• The baseline built gem rejected the reproducing configuration with a false unexpected-EOF error; the candidate built gem accepted it with fluentd --dry-run; a genuinely unterminated double-quoted value remained rejected.
• Ran the candidate built gem as a separate fluentd --no-supervisor process through dummy → record_transformer → stdout and externally parsed its emitted JSON as {"message":"seed","blank":"world\n\n","literal_backslash":"left\\\nright","continued":"leftright"}.

[Watson1978]

Nice fix.

The token-based handling of line breaks reads much more clearly than the old [^"]-plus-line-end pairing. The small follow-up suggestions on the same change.

[Watson1978]

Please remove now unused constant in

fluentd/lib/fluent/config/basic_parser.rb

Line 31 in bc40b6f

LINE_END_WITHOUT_SPACING_AND_COMMENT = /(?:\z|[\r\n])/

And, add constants instead, like

  # A physical line break (LF, CR, or CRLF) inside a double-quoted string.
  # It is preserved as-is in the resulting value.
  LINE_BREAK = /\r\n|[\r\n]/
  # A backslash immediately followed by a physical line break.
  # It works as a line continuation, so both are stripped from the value.
  LINE_CONTINUATION = /\\#{LINE_BREAK}/o

and use them

          elsif skip(LINE_CONTINUATION)
            next
          elsif s = scan(LINE_BREAK)