feat: add configurable log line length limits to prevent DoS attacks

[GingerGraham]

• fixes [BUG] No Input Length Limits #41

[Copilot]

Pull request overview

This pull request implements configurable log line length limits as a defense-in-depth measure against denial-of-service attacks through excessively large log messages. It addresses issue #41 which identified that the library lacked input length limits, potentially allowing rapid disk space consumption, performance degradation, and journal message size issues.

Changes:

• Adds _truncate_log_message() internal function with robust edge case handling for message truncation
• Implements separate configurable limits for console/file output (LOG_MAX_LINE_LENGTH) and journal output (LOG_MAX_JOURNAL_LENGTH) with 4096-byte defaults
• Provides CLI flags (--max-line-length, --max-journal-length) and configuration file options for customization

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
logging.sh	Core implementation: adds global limit variables, _truncate_log_message() function, CLI argument parsing, config file parsing, and integration into message logging flow
tests/test_output.sh	Adds functional test for message truncation with formatted output validation
tests/test_config.sh	Adds test for configuration file parsing of length limit settings
docs/initialization.md	Documents new CLI options in initialization reference
docs/configuration.md	Documents configuration keys, aliases, defaults, and example usage
docs/api-reference.md	Updates API reference table with new initialization options
docs/journal-logging.md	Explains DoS mitigation context for journal message limits
configuration/logging.conf.example	Adds example configuration with comments
README.md	Adds DoS resistance feature to highlights list