[Feature] Be able to leverage package to create MRR reports

### Is there an existing feature request for this?

- [X] I have searched the existing issues

### Describe the Feature

Update daily overview model, or a more fitting model, to account for subscription-based transactions in order to build MRR reports on top of our package.

We need the invoice table in order to connect to the subscription table, which the daily overview model currently doesn't pull from. The closest model that would feed into an MRR report I'd say is the [invoice_line_item_details](https://fivetran.github.io/dbt_stripe/#!/model/model.stripe.stripe__invoice_line_item_details) model.

It seems that the daily overview model amounts come from the balance transaction table. The way subscription data would be brought in would be: balance transaction > charge > invoice > subscription. The most downstream models where some of them exist together is in the [balance transactions](https://fivetran.github.io/dbt_stripe/#!/model/model.stripe.stripe__balance_transactions) and [subscription details](https://fivetran.github.io/dbt_stripe/#!/model/model.stripe.stripe__subscription_details) . But there isn't a model that ties all of those source tables together.

### Describe alternatives you've considered

_No response_

### Are you interested in contributing this feature?

- [X] Yes.
- [ ] Yes, but I will need assistance and will schedule time during your [office hours](https://calendly.com/fivetran-solutions-team/fivetran-solutions-team-office-hours) for guidance.
- [ ] No.

### Anything else?

_No response_

Start by reading the daily overview model alongside invoice_line_item_details, balance transactions, and subscription details to map the existing model relationships. Trace the proposed balance transaction > charge > invoice > subscription path, then define the model change needed to support MRR reporting and verify that the resulting data connects subscription-based transactions correctly.

Written by the indexing model from the issue text.