query_history: Reduce amount of indexed data down to 1 day

[ParkMyCar]

As it says in the title!

Motivation

Fixes https://github.com/MaterializeInc/database-issues/issues/8938

Checklist

• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
• If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

[JLDLaughlin]

🚢

[SangJunBak]

In this PR, would we be able to add access: vec![SUPPORT_SELECT, ANALYTICS_SELECT, MONITOR_REDACTED_SELECT, MONITOR_SELECT], to mz_prepared_statement_history or just [PUBLIC_SELECT]? Otherwise we aren't able to join MZ_RECENT_SQL_TEXT_REDACTED, mz_statement_execution_history_redacted, and mz_prepared_statement_history for mz_support users. Alternatively, we can create a new view called MZ_ACTIVITY_LOG_THINNED_REDACTED that hides the error_message

[SangJunBak]

Talked it over with Parker and he agreed. Added 46b80bf (#31250)