ref(crons): Reorganize incident creation / issue occurrence logic

[adamsaimi]

Test 8

[adamsaimi]

[Bug] Duplicate Incident Creation

• Problem: When failure_issue_threshold > 1, create_incident_occurrence is incorrectly called multiple times, resulting in failure_issue_threshold Kafka messages for a single incident and unnecessary load.
• Fix: Modify the logic to ensure create_incident_occurrence is called only once per incident creation, using the most recent failed check-in and all previous_checkins for context.

        # Only create one occurrence for the incident, using the most recent failed_checkin
        # and the full list of previous_checkins for context.
        create_incident_occurrence(
            previous_checkins,
            failed_checkin, # Use the single failed_checkin that triggered this call
            incident,
            received=received,
        )```

[adamsaimi]

[Security] Potential Information Leakage

• Problem: The monitor_environment.monitor.config is directly included in the event context, which could expose sensitive information like API keys or internal paths.
• Fix: Explicitly filter or sanitize the config dictionary to include only non-sensitive, relevant fields before adding it to the event context.

        # ... other fields ...
        \"config\": {k: v for k, v in monitor_environment.monitor.config.items() if k not in [\"sensitive_key_1\", \"sensitive_key_2\"]}, # Example filtering
        # ... other fields ...
    }```