Create historical versions of source statistics built in views

[SangJunBak]

Due to an issue with latency and high CPU usage, we create a non-historical index + view on top of mz_source_statistics such that Console's source lists efficiently query on it. The latency and high CPU usage is related to us retaining history, causing the number of updates in the index to be large.

From 5 cases, there seems to be a stark improvement with these new indexes:

Motivation

Tips for reviewer

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).
• This PR includes the following user-facing behavior changes:

[RobinClowers]

I'm not sure how this works, but does renaming those indexes mean we will loose all the existing historical data?

[maddyblue]

This will need signoff from the epd-mz-introspection-council due to a new index.

[maddyblue]

If this name is staying, it should keep its old oid. Give VIEW_MZ_SOURCE_STATISTICS_WITH_HISTORY_OID and the other new thing new oids instead.

[SangJunBak]

I'm not sure how this works, but does renaming those indexes mean we will loose all the existing historical data?

@RobinClowers My first guess would be no given the historical view derives from MZ_SOURCE_STATISTICS_RAW that has the existing historical data so this new index would hydrate with the same state. I'll let @maddyblue weigh in tho

[maddyblue]

You can run REWRITE=true bin/cargo-test -p mz-environmentd --test server test_http_sql to fix the failing tests in mz-environmentd::server test_http_sql.

To fix the sqllogictests run ./bin/sqllogictest -- --postgres-url $COCKROACH_URL test/sqllogictest/cluster.slt test/sqllogictest/information_schema_tables.slt test/sqllogictest/mz_introspection_index_accounting.slt test/sqllogictest/oid.slt --rewrite-results

The testdrive test will need manual rewriting, but its diff is printed in the test failure output so should be applied by hand. I'm not going to push up a fix for these because I think changing the oids as requested will result in more changes, but these may be enough to unblock you.

[chaas]

LGTM from mz_introspection council. The new index has only a very small number of records, so the memory impact should be minimal.

[maddyblue]

Good chance that the autogenerated/docs tests will fail due to the new things not being documented. ./ci/test/lint-docs-catalog.sh --rewrite may help there, and probably need to add docs.