release-26.3: roachtest: activerecord failed

roachtest.activerecord failed with artifacts on release-26.3 @ 038fbd3b2f63f29429283d3b09c5c551ea69ecf3:

Failed with:

(orm_helpers.go:225).summarizeFailed: 
Tests run on Cockroach v26.3.2-dev-038fbd3b2f63f29429283d3b09c5c551ea69ecf3
Tests run against activerecord 8.1.0
8905 Total Tests Run
8902 tests passed
3 tests failed
45 tests skipped
60 tests ignored
0 tests passed unexpectedly
2 tests failed unexpectedly
0 tests expected failed but skipped
0 tests expected failed but not run
---
--- FAIL: HasAndBelongsToManyAssociationsTest#test_destroy_associations_destroys_multiple_associations (unexpected)
--- PASS: SerializedAttributeTest#test_unexpected_serialized_type (expected)
--- FAIL: HasAndBelongsToManyAssociationsTest#test_destruction_does_not_error_without_primary_key (unexpected)
--- PASS: SerializedAttributeTestWithYamlSafeLoad#test_unexpected_serialized_type (expected)
For a full summary look at the activerecord artifacts 
An updated blocklist (activeRecordBlocklist) is available in the artifacts' activerecord log
test artifacts and logs in: /artifacts/activerecord/run_1

Cluster Node to Ip Mapping:

Parameters:

• arch=amd64
• cloud=gce
• coverageBuild=false
• cpu=4
• diskCount=0
• encrypted=false
• fs=ext4
• localSSD=true
• metamorphicDRPC=true
• metamorphicLeases=leader
• runtimeAssertionsBuild=false

Jira issue: CRDB-68568

The failure is summarized at orm_helpers.go:225; begin by inspecting the ActiveRecord artifacts under /artifacts/activerecord/run_1 and the two failing HasAndBelongsToManyAssociationsTest cases. Use the roachtest README to rerun the ActiveRecord compatibility test against commit 038fbd3b2f63f29429283d3b09c5c551ea69ecf3, then identify the cause and make both unexpected failures pass.