Update csrf_protect_m import for Django 6.0

[ulgens]

Proposed changes

Django 6.0 removes contrib.auth.admin.csrf_protect_m: https://github.com/django/django/pull/18466/files

This PR updates an import of the removed decorator to a still-existing one.

Types of changes

What types of changes does your code introduce to DjangoTypesense?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

• I have read the CONTRIBUTING doc
• Lint and unit tests pass locally with my changes
  • Current main doesn't pass pre-commit checks
• I have added tests that prove my fix is effective or that my feature works
  • I can update the test matrix but it seems there are multiple EOL Python / Django versions in it. I'm worried that a simple addition of Django 6.0 won't cut it.
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

[EricOuma]

Hey @ulgens
I have removed Python 3.8 support. Please pull the new main to your branch.

Does your change support the Django versions in https://github.com/Siege-Software/django-typesense/blob/main/.github/workflows/build.yml

[ulgens]

@EricOuma Hey, if you mean #108 it's not merged yet. I'll rebase my branch from the latest main when it's merged, thank you.

[ulgens]

@EricOuma

Does your change support the Django versions in https://github.com/Siege-Software/django-typesense/blob/main/.github/workflows/build.yml

The import path I use in the PR was added 16 years ago: django/django@4bff194 I think it's perfectly safe to use, even for Django 3.2

[ulgens]

@EricOuma Hey 👋🏻 Any chance to revisit this?