Unapplied migrations on clean clone

Right after cloning this repo and running it, I get a warning in red text that reads:

```
You have 18 unapplied migration(s). Your project may not work properly until you apply the migrations for app(s): admin, auth, contenttypes, sessions.
Run 'python manage.py migrate' to apply them.
```

Steps to reproduce:
1. Use any reasonable Linux machine (in my case, an up-to-date CachyOS install)
2. `git clone git@github.com:Azure-Samples/msdocs-python-django-webapp-quickstart.git`
3. `cd msdocs-python-django-webapp-quickstart/`
4. `python -m venv .venv`
5. `source .venv/bin/activate.fish` (I use the Fish shell, but should make no difference)
6. `pip install -r requirements.txt`
7. `python manage.py runserver`
8. Observe

Entire output:

```
~/(...)/msdocs-python-django-webapp-quickstart main
.venv ❯ python manage.py runserver
Watching for file changes with StatReloader
Performing system checks...

System check identified no issues (0 silenced).

You have 18 unapplied migration(s). Your project may not work properly until you apply the migrations for app(s): admin, auth, contenttypes, sessions.
Run 'python manage.py migrate' to apply them.
June 12, 2026 - 14:02:50
Django version 6.0.6, using settings 'quickstartproject.settings'
Starting development server at http://127.0.0.1:8000/
Quit the server with CONTROL-C.

WARNING: This is a development server. Do not use it in a production setting. Use a production WSGI or ASGI server instead.
For more information on production servers see: https://docs.djangoproject.com/en/6.0/howto/deployment/

```

The server runs fine.

Start by reproducing the clean-clone setup with requirements.txt and manage.py runserver, then inspect how this startup path handles Django migrations. Confirm the expected behavior after the relevant startup change by repeating the listed steps and checking whether the unapplied-migrations warning still appears.

Written by the indexing model from the issue text.