Merged PR 4530: first comment time added

# Description

First comment time added

# Checklist

- [x] The edited models and dependants run properly with production data.
- [x] The edited models are sufficiently documented.
- [x] The edited models contain PK tests, and I've ran and passed them.
- [ ] I have checked for DRY opportunities with other models and docs.
- [ ] I've picked the right materialization for the affected models.

# Other

- [ ] Check if a full-refresh is required after this PR is merged.

first comment time added

Related work items: #27812

models/reporting/resolutions/resolutions__incidents.sql

@@ -17,6 +17,7 @@ select
     first_comment_at_utc as first_comment_at_utc,
     last_comment_at_utc as last_comment_at_utc,
     comment_count as comment_count,
+    time_to_first_comment_in_hours as time_to_first_comment_in_hours,
     first_status_at_utc as first_status_at_utc,
     last_status_at_utc as last_status_at_utc,
     resolution_time_in_hours as resolution_time_in_hours,

models/reporting/resolutions/schema.yml

@@ -71,6 +71,14 @@ models:
         data_type: bigint
         description: "Number of comments submitted on the incident."
 
+      - name: time_to_first_comment_in_hours
+        data_type: numeric
+        description: "Time taken to reach the client for the first time."
+        data_tests:
+          - dbt_expectations.expect_column_values_to_be_between:
+              min_value: 0
+              strictly: true
+
       - name: first_status_at_utc
         data_type: timestamp
         description: "Timestamp of the first status change on the incident."