fix(django-spanner): declare django dependency in setup.py

[hebaalazzeh]

Description

Declares "django >= 5.2, < 5.3" in install_requires (dependencies) for django-google-spanner.

Motivation

django_spanner imports and requires django directly at top-level import time and explicitly checks for Django 5.2 compatibility in django_spanner/__init__.py.

Without django listed in setup.py, installing django-google-spanner in a clean environment (such as during the import-profiler presubmit check) caused imports to fail with: ModuleNotFoundError: No module named 'django'

Tracking issue for Django 6.0 support: #18053

[gemini-code-assist]

Code Review

This pull request updates the CI script ci/run_single_test.sh to install django~=5.2 as a peer dependency when testing the django-google-spanner package. The reviewer points out that hardcoding Django 5.2 can cause installation failures on Python versions older than 3.10, and suggests relaxing the constraint to just django so that pip can automatically resolve the latest compatible version.

[parthea]

Can we add the required dependency instead?

google-cloud-python/packages/django-google-spanner/setup.py

Line 21 in e82ad65

dependencies= ["sqlparse >= 0.3.0", "google-cloud-spanner >= 3.13.0"]

[hebaalazzeh]

I updated packages/django-google-spanner/setup.py to declare "django >= 5.2, < 5.3" in dependencies and reverted the CI script workaround.