Fix negative multiplicities caused by v80->v81 catalog migration

[SangJunBak]

Rebased off and dependent on #36524

Motivation

Creates a regression test for fixing negative multiplicities caused by caused by v80->v81 catalog migration seen in incident-1007

Description

• Adds a v82 to v83 migration that fixes forward and clears out any negative multiplicities.

Verification

How do you know this change is correct? Describe new or existing automated
tests, or manual steps you took.

[def-]

Nightly triggered, I'll take a closer look at the code now: https://buildkite.com/materialize/nightly/builds/16399

Edit: Fixed the miri test failures.

[def-]

Upgrade tests can't run in Test pipeline, they are way too slow. Should be moved to Nightly. I would also prefer if this was caught in platform-checks additionally, not just with those specific versions, but with any version in the future exhibiting similar bugs.
I'll try add it to platform-checks.

[def-]

I'm not sure if we still need this test at all then, we could add a scenario to platform checks that does these versions too one we add the scenario that catches it by altering the role and then selecting from the catalog.

[def-]

The entire file smelly pretty LLMy, I think we shouldn't have one mzcompose.py test per bug/incident we run into, but use the existing frameworks when appropriate, so that we find similarly shaped bugs more generally.

[SangJunBak]

Fair point!

[def-]

I pushed platform checks extensions that would have caught this:

source: /home/deen/git/materialize/misc/python/materialize/checks/all_checks/password_auth.py:114
2:1: error: executing postgres query: db error: ERROR: Invalid data in source, saw retractions (1) for row that does not exist: [Map({"key": Map({"id": Map({"User": Numeric(<#>)})}), "kind": String(<"XXXX">), "value": Map({"attributes": Map({"auto_provision_source": JsonNull, "inherit": True, "login": True, "superuser": JsonNull}), "membership": Map({"map": List([])}), "name": String(<"XXXX#">), "oid": Numeric(<#####>), "vars": Map({"entries": List([])})})})]
     |
   1 |
   2 | $ postgres-execute c ... [rest of line truncated for security]
     | ^

Test run on this PR now: https://buildkite.com/materialize/nightly/builds/16406

Edit: Removed it for now, I'll do it in a separate PR so that we can merge this test already.

[def-]

Upgrade tests can't run in Test pipeline, they are way too slow. Should be moved to Nightly. I would also prefer if this was caught in platform-checks additionally, not just with those specific versions, but with any version in the future exhibiting similar bugs.
I'll try add it to platform-checks.