remove django model related testing

[to-sta]

Contributor checklist

• This pull request is on a separate branch and not the main branch
• I have run the tests for the backend and frontend depending on what's needed for my changes as described in the testing section of the contributing guide

---

Description

As discussed in the dev sync, I removed the tests within groups testing, that are django model settings. I also encoutered the i18n_check error again and uncommented the pre-commit check for it, because it prevented me from making this PR.

Related issue

• No related issue

[netlify]

✅ Deploy Preview for activist-org canceled.

Name	Link
🔨 Latest commit	1c09bce
🔍 Latest deploy log	https://app.netlify.com/sites/activist-org/deploys/6764b523fa2468000890d353

[github-actions]

Thank you for the pull request!

The activist team will do our best to address your contribution as soon as we can. The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and Development rooms once you're in. Also consider joining our bi-weekly Saturday dev syncs. It'd be great to have you!

Maintainer checklist

• The TypeScript and formatting workflows within the PR checks do not indicate new errors in the files changed

• The Playwright end to end and Zap penetration tests have been ran and are passing (if necessary)

• The changelog has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

[andrewtavis]

Note @to-sta that you can disable the checks with git commit --no-verify -m "COMMIT_MESSAGE" :)

[andrewtavis]

I'm hoping that c68a358 will fix the i18n checks for you, @to-sta. I figure it was the hard coded Unix style paths :) Let me know if it's still a problem though!

[andrewtavis]

Thanks for the fixes here, @to-sta! The frontend checks will end up being problematic for a moment, but the backend ones are fine now :)