Switch to conventionally named version tables

[nimmolo]

Turns out the default behavior of the gem is to name the columns like "location_versions", which is what i believe we want.
We've been overriding the default to make them "locations_versions".

This PR removes the overrides and migrates to the default table names.

I think this will break old migrations. I'll need to update them (?!)

[JoeCohen]

1. I'm curious why we're doing this.
2. Would it make any sense to declare acts_as_versioned bankruptcy and switch to a maintained versioning gem.
   I'm pretty sure we'd have to abandon all the old versions and start from scratch. The last time I looked a this there wasn't a path from acts_as_versioned to a newer gem.
   (I also wonder if acts_as_versioned is thread safe.)

[pellaea]

You're right, Joe. The reason we kept acts_as_versioned alive was because it was so much work to migrate the old tables to the new ones. Surely that's important, right? We aren't actually considering removing all editing changes ever made on the site?

…

On Sat, Mar 2, 2024 at 10:41 PM Joseph D. Cohen ***@***.***> wrote: 1. I'm curious why we're doing this. 2. Would it make any sense to declare acts_as_versioned bankruptcy and switch to a maintained versioning gem. I'm pretty sure we'd have to abandon all the old versions and start from scratch. The last time I looked a this there wasn't a path from acts_as_versioned to a newer gem. (I also wonder if acts_as_versioned is thread safe.) — Reply to this email directly, view it on GitHub <#1990 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAYTNNOS4U4TB5ISC7UWOVTYWKLWXAVCNFSM6AAAAABEDSD2BWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZVGAYDQOJVGE> . You are receiving this because you commented.Message ID: ***@***.***>

[coveralls]

coverage: 94.421%. remained the same
when pulling 36f4f16 on nimmo-version-tables
into 26dcd40 on main.