fix: use django's undeprecated gettext_lazy

[kevr]

This commit solves deprecation warnings produced by django.

Signed-off-by: Kevin Morris kevr@0cost.org

[alvindera97]

I guess the maintainer isn't available anymore 🥲 .... Another solution might be to maintain a fork for the foreseeable future. However I've been asking myself what amount of benefit this package brings apart from approximately O(1) look up times. If there are millions of rows, then maybe I could get the motivation for this. At that point, wouldn't it be better to think of better native O(1) array-like-collection lookup databases/fields?

Or maybe it's somewhere in Postgres's documentation and I've not seen it yet.