[Feature] Include active_devices_last_30_days as a field

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

- [x] I have searched the existing issues

### Describe the Feature

As mentioned in the current DECISIONLOG, fields such as `active_devices_last_30_days` are not included in our end models. This is because we create the reports off of daily tables directly from the Apple App Store, so we do not have insight into how to de-duplicate counts that would ensure devices don't get accounted for more than once over 30 days. However, if you would like to see this field supported in the future, feel free to comment or follow this ticket.

### How would you implement this feature?

Include previously excluded fields

### Describe alternatives you've considered

_No response_

### Are you interested in contributing this feature?

- [x] Yes.
- [ ] Yes, but I will need assistance.
- [ ] No.

### Anything else?

_No response_

Start by reading the current DECISIONLOG and tracing the end models back to the daily Apple App Store tables. Determine how devices can be de-duplicated across a 30-day period before adding active_devices_last_30_days. Done means the field is supported in the end models with counts that do not account for a device more than once in 30 days.

Written by the indexing model from the issue text.