I don't know if it's the same thing, but in some of my early playing around with upgrading a site to v14 I did I was also using the traditional/attended method, and ran into a similar SQL error around a missing 'key' column. I was only able to get past it and complete the upgrade by turning on unattended upgrades instead in appsettings.json temporarily after which if it all upgrades fine it can be disabled again. But I never got to the bottom of what caused it as my tests upgrading other v13 sites were all fine. However I do know the problem site in question had also originally been on v10 so if this is the same thing, it could be it's something to do with a site that's seen a few version jumps.