1633: Update Django dependency to version 5.1.5

[ulgens]

https://docs.djangoproject.com/en/5.1/releases/5.1/
https://docs.djangoproject.com/en/5.1/releases/5.1/#backwards-incompatible-5-1

Resolves #1633

[ulgens]

@bmispelon The failure in the test looks like a flake but I don't have permission to re-run the pipeline. I'm checking this again.

[bmispelon]

The test failure looks like it might have something to do with tracdb.test_utils.TracDBCreateDatabaseMixin. It might be a fluke, but it might also be genuine (it could be that the mixin relied on an internal Django API that was modified).

You might be able to reproduce the failure locally by running all tests (not just a subset).

[ulgens]

I'm trying to reproduce it locally but turned out creating the local env was harder than I remember, and docker setup is not ready for local testing. When I find a quick solution on this, I'll be creating several other issues 🙂

[ulgens]

It looks like the errors are somehow related to composite PKs, but I thought it was merged after 5.1, and I couldn't find anything related on the 5.1 changelog. I'll try to tackle it another day, but if it's really about composite PKs, I guess it will require bigger changes than I thought.

Added another comment on https://github.com/django/djangoproject.com/pull/1479/files#r1924320453

[pauloxnet]

I'm trying to reproduce it locally but turned out creating the local env was harder than I remember, ...

Please open an issue for the Readme if you found that something is missing or wrong.

Write here if you need help in the local setup.

[bmispelon]

Using git bisect on the Django repo, I found that our tests started breaking after this change: django/django@e65deb7

This points further to something being broken with the TracDBCreateDatabaseMixin hack. I'll look further into it. 🔬

[bmispelon]

Don't ask me how it works, but I just pushed a commit that fixes the tests 😅

[ulgens]

I feel like we pushed the bug into the 5.2 update 😬 but I'm okay with passing tests for now ✨

[bmispelon]

I feel like we pushed the bug into the 5.2 update 😬 but I'm okay with passing tests for now ✨

I tried and the tracdb tests still pass with 5.2 so I think we should be good on that front. And once we have 5.2 we should be able to get rid of all the hacks and use real composite primary keys I think 🎉

I think all is good with this PR now, I'm going to squash all the commits then merge, let's see how the deploy goes 🤞🏻