Fix postal abbreviations for Connecticut and Kansas

[JosiahDub]

Creates migrations to fix slugs that end with incorrect postal abbreviations using regular expression replacements.

Core models like MapGroup and Map have slugs, but I do not have enough experience to know if they use Place or Page slugs. These migrations can be copied and adapted to these models if needed.

Legacy URLs that people might have bookmarked will break. It might be possible to create a redirect if an incorrect abbreviation is found.

Closes #230

[mradamcox]

@JosiahDub Thank you submitting this and the work you did to put it together! It's the first code-related PR I've received so it will take me a little bit of time to fully test and review it.

For this type of db change I often write a one-off management command and then just manually run it on the two instances of the app that I have in production, but seems like it may be time to handle things more formally in migrations.

This particular approach will be a good stop-gap measure because I have been wanting to overhaul the entire Place database content for a while, but there is no need to do all of that to just fix these problematic abbreviations.

One change you can make though is that the Page slugs don't have anything to do with the postal abbreviations, so there is no need for a migration in that app. Pages are just extra markdown content and there are only a few in the production db, like /about, /faq, /contact, etc.

I will add redirects to the production db after we complete this PR.

Thank you!

[mradamcox]

Hi, did the test suite pass for you? I am getting this error:

CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0001_initial, 0002_fix_postal_slugs in places; 0002_partner, 0003_fix_postal_slugs in frontend).

[JosiahDub]

Hi, did the test suite pass for you? I am getting this error:

I wrote the migrations manually and forgot to add dependencies. I added them now. Unfortunately I'm having trouble running the test suite due to gdal library issues on my Mac. brew installs 3.12 by default, which django 6.0 does not even support. Very annoying. I'll keep trying to get them running.

Migrations might be overkill for just updating some fields. Personally I might not have even written a management command. I probably would have just fixed it in the console.

By the way, I purposely chose an easy looking issue just to get familiar with the code base. It's marked as low priority so if you have other high priority tickets I'm happy to let this stew for a bit.