update stripe package with running total model

[fivetran-reneeli]

Are you a current Fivetran customer?

Internal What change(s) does this PR introduce?

• Introduces a running_total model to alleviate runtime errors resulting from the daily_overview model exceeding disc capacity upon running. Did you update the CHANGELOG?
• [ ] Yes

Does this PR introduce a breaking change?

• [x] Yes (please provide breaking change details below.)
• [ ] No (please provide an explanation as to how the change is non-breaking below.)

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)

• [x] Yes

Is this PR in response to a previously created Bug or Feature Request

• [x] Yes, Issue/Feature [link bug/feature number here]
• [ ] No

How did you test the PR changes?

• [x] BuildKite
• [ ] Local (please provide additional testing details below)

Select which warehouse(s) were used to test the PR

• [x] BigQuery
• [x] Redshift
• [x] Snowflake
• [x] Postgres
• [x] Databricks
• [x] Other (provide details below)

Provide an emoji that best describes your current mood

:dancer: **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](https://www.surveymonkey.com/r/DQ7K7WW) on our existing dbt packages or what you'd like to see next.

[fivetran-reneeli]

• [ ] docs regen

[fivetran-reneeli]

Thanks for the review @fivetran-catfritz! -- update: actually, after talking with Joe, I think we should keep the materialization as a table because view would not solve the compute issue. Though i'm working through how to avoid having the duplicate tables, gonna see what happens if we just move what we had in the int model to the final daily overview model