Implement Command-Line Flags Parsing for Events, Source, and Enrichment

[ShohamBit]

Background
We’re introducing command-line flags to complement the config file. Users should be able to specify or override configurations directly through flags. In this phase, we’ll focus on implementing and parsing flags related to Events, Source, and Enrichment settings.

Tasks

Event Flags

• --event <event_name>.version=<version>: Parse and apply event version.
• --event <event_name>.data-fields=<fields>: Parse and apply event data fields.

Source Flags

• --source file=<path>: Set the source file path for events.

Enrichment Flags

• --enrich container.enabled=<true/false>: Enable or disable container enrichment.
• --enrich resolve-fd=<true/false>: Enable or disable file descriptor resolution.
• --enrich exec-hash.enabled=<true/false>: Enable or disable execution hash calculation.
• --enrich exec-hash.mode=<mode>: Set the mode for execution hash calculation (inode, dev-inode, or digest-inode).
• --enrich user-stack-trace=<true/false>: Enable or disable user stack trace enrichment.

Acceptance Criteria

• Flags can be parsed without errors.
• Correct validation:
  • Invalid values produce clear error messages.
  • Missing required parts (like <event_name>) result in helpful error messages.
• Flag settings are stored in a structured format ready to be merged with config file settings.

Why This Matters
By allowing users to specify and override these particular configurations via flags, we offer flexibility and control. This helps users test scenarios or quickly change settings without modifying their config file, ultimately making the system more user-friendly and adaptable.

[yanivagman]

Part of #4453