feat(sources): add disconnect_mode option to tcp sources

[tronboto]

Summary

Adds a disconnect_mode configuration option to TCP sources (socket, logstash, fluent, syslog, statsd) that controls how connections are closed on shutdown or when max_connection_duration_secs elapses.

The two modes are:

• drain (default for socket, syslog, statsd) - sends a FIN and waits for the client to close. Existing behaviour.
• abort (default for logstash, fluent) - sets SO_LINGER=0 to force close immediately with RST.

The original motivation is "write-only" clients such as Serilog.Sinks.Network that never read from the socket and therefore cannot detect a graceful shutdown. Additionally, the "reference implementations" for the beats (logstash) and fluent protocols also use an abort style shutdown:

• Logstash beats input
• Fluentd server

This change also fixes a pre-existing bug where shutdown(SHUT_WR) would be called repeatedly on every loop iteration after max_connection_duration_secs elapsed, rather than just once. The kernel ignores subsequent calls but it's still wasteful.

Vector configuration

sources:
  tcp_in:
    type: socket
    mode: tcp
    address: "0.0.0.0:9000"
    shutdown_timeout_secs: 5
    disconnect_mode: abort
sinks:
  out:
    type: console
    inputs: [tcp_in]
    encoding.codec: text

How did you test this PR?

• Manual testing with netcat and a write-only Python client against both modes, verifying FIN and RST behaviour using tcpdump.
• A new unit test added to sources::socket:
  • tcp_disconnect_mode_abort_on_shutdown - verifies RST is received immediately on shutdown.

Change Type

• New feature

Is this a breaking change?

• Yes (default disconnect_mode for logstash and fluent changes from drain to abort)

Does this PR include user facing changes?

• Yes - changelog fragment created

References

Closes #23855

Notes

• Please read our Vector contributor resources.
• Do not hesitate to use @vectordotdev/vector to reach out to us regarding this PR.
• Some CI checks run only after we manually approve them.
  • We recommend adding a pre-push hook, please see this template.
  • Alternatively, we recommend running the following locally before pushing to the remote branch:
    • make fmt
    • make check-clippy (if there are failures it's possible some of them can be fixed with make clippy-fix)
    • make test
• After a review is requested, please avoid force pushes to help us review incrementally.
  • Feel free to push as many commits as you want. They will be squashed into one before merging.
  • For example, you can run git merge origin master and git push.
• If this PR introduces changes Vector dependencies (modifies Cargo.lock), please
  run make build-licenses to regenerate the license inventory and commit the changes (if any). More detail s on the dd-rust-license-tool.