logictest: add local-mixed-23.1-23.2 as a default config

[rafiss]

informs #103956

This ensures that we test logic tests with a system schema bootstrapped from 23.1.

This also renames local-mixed-22.2-23.1 to instead to be local-mixed-22.2-23.2, since we want to test skipping version 23.1.

Release note: None

[cockroach-teamcity]

This change is 

[rafiss]

@postamar I tried making a new logictest config like this:

	{
		Name:                        "local-mixed-23.1-23.2",
		NumNodes:                    1,
		OverrideDistSQLMode:         "off",
		BootstrapVersion:            clusterversion.V23_1,
		DisableUpgrade:              true,
		DeclarativeCorpusCollection: true,
	},

However, the test setup fails here:

cockroach/pkg/sql/logictest/logic.go

Lines 1883 to 1889 in 795dd78

	// Only create the test database on the initial cluster, since cluster restore
	// expects an empty cluster.
	if _, err := t.db.Exec(`
	CREATE DATABASE test; USE test;
	`); err != nil {
	t.Fatal(err)
	}

with the error:

    logic.go:1888: pq: unexpected value: raw_bytes:"J\013\341S\003\022Y\n\tdefaultdb\020d\0320\n\013\n\005admin\020\002\030\002\n\r\n\006public\020\200\020\030\000\n\n\n\004root\020\002\030\002\022\004root\030\002\"\000(\001:\014\n\006public\022\002\010e@\000J\000Z\002\020\000" timestamp:<wall_time:1686864046932492476 >

This seems like it might have something to do with the initialvalues for V23_1. Do you have any ideas for how to debug this?

[postamar]

As discussed this looks like the failure of a CPut to system.descriptor. Those are performed by the descs.Collection.

That's the proximal cause however, deeper down I suspect it's related to the test cluster not being set up correctly somehow; we're doing something relatively new and, until now, uncommon, in which we start a test cluster at a version which is neither the min-supported version or the binary version. I'm curious how mixed-version clusters started using the go-testserver framework will behave.

[rafiss]

#112122 replaced this