Schedule weekly reports to run Monday for the previous week

[h-m-m]

🎫 Ticket

Link to the relevant ticket:
LG-13559

🛠 Summary of changes

We're missing data for Sunday in the weekly report because the report runs Sunday morning. This delays the report until Monday and then runs it for the previous week.

📜 Testing Plan

We can confirm in staging that this change schedules the expected report

[zachmargolis]

let's add a freeze_time around these specs

[h-m-m]

❓ @zachmargolis Do we do this automatically because of:

identity-idp/spec/rails_helper.rb

Lines 134 to 136 in cff618e

	config.around(:each, freeze_time: true) do |example|
	freeze_time { example.run }
	end

[zachmargolis]

That only applies to specs/groups with a freeze_time: true tag, I didn't see that here?

[zachmargolis]

LGTM but I would definitely prefer an explicit freeze_time before merging

[h-m-m]

LGTM but I would definitely prefer an explicit freeze_time before merging

Sure, that's reasonable and understandable. Updated

[zachmargolis]

Looks like this is failing in CI due to our commit message changelog requirement (logs link)

A valid changelog line was not found.
A commit message should contain a line in the form of:
changelog: CATEGORY, SUBCATEGORY, CHANGE_DESCRIPTION
example:
changelog: User-Facing Improvements, WebAuthn, Improve error flow for WebAuthn (LG-5515)
categories:
- User-Facing Improvements
- Bug Fixes
- Internal
- Upcoming Features
Include "[skip changelog]" in a commit message to bypass this check.
Note: the changelog message must be separated from any other commit message by a blank line.

[h-m-m]

Looks like this is failing in CI due to our commit message changelog requirement (logs link)

Thanks for the handy link. Fixed ✔️