Add enhancements to track fin ai usage

[daniel-nagish]

Please provide your name and company

Link the issue/feature request which this PR is meant to address
#61
#59

Detail what changes this PR introduces and how this addresses the issue/feature request linked above.

making the following updates:
models/intermediate/int_intercom__conversation_part_aggregates.sql

• Add differentiation for FinAI involvement in ticket handling, allowing for more granular analytics
  by adding counts for total, admin parts, and bot parts
• adding additional breakdowns of all the other aggregate metrics to have for both admin (human) and bot (ai)
  ie first_bot_response in addition to first_admin_response

models/intermediate/int_intercom__conversation_string_aggregates.sql

• add an aggregation for all types (lead, admin, bot) that touched a given conversation

models/intermediate/int_intercom__conversation_part_events.sql

• add a cte for bot events following the logic from admin_events, except changing the filter to author_type='bot'

models/intercom__conversation_enhanced.sql

• add in ai_resolution_stage from the conversation_history table to allow for better tracking of that
• add in logic for breaking down the platform the user reached out for support on

models/intercom__conversation_metrics.sql

• similar to the above, but also add in the admin metadata so you can drill down by support rep vs ai

How did you validate the changes introduced within this PR?
ran a dev pipeline run to confirm the numbers lined up with intercom reports and did not introduce breaking changes

Which warehouse did you use to develop these changes?
Bigquery

Did you update the CHANGELOG?

• Yes

Did you update the dbt_project.yml files with the version upgrade (please leverage standard semantic versioning)? (In both your main project and integration_tests)

• Yes

Typically there are additional maintenance changes required before this will be ready for an upcoming release. Are you comfortable with the Fivetran team making a few commits directly to your branch?

• Yes
• No

If you had to summarize this PR in an emoji, which would it be?

🎩
😎
Feedback

We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your feedback on our existing dbt packages or what you'd like to see next.

PR Template

• Community Pull Request Template (default)

• Maintainer Pull Request Template (to be used by maintainers)