Update the docs when overriding django_db_setup

[kingbuzzman]

Fixes issue: #1183 #1131

See: #1183 (comment)

[kingbuzzman]

@bluetech thoughts?

[bluetech]

Not a review -- I need to look into it more. Just a couple of typos.

[kingbuzzman]

@bluetech thoughts?

[Copilot]

Pull Request Overview

Updates documentation examples for overriding the django_db_setup fixture to correctly use the request parameter and call the original fixture via request.getfixturevalue(). This addresses reported issues where the previous examples would not work properly.

• Adds request parameter to django_db_setup fixture signatures
• Changes from bare yield to yield request.getfixturevalue("django_db_setup")
• Updates database configuration example to use individual key assignment instead of dictionary replacement

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.}

[Copilot]

This creates a circular dependency where django_db_setup tries to get its own fixture value. The correct approach would be to yield from the original fixture or use a different fixture name for the override.

Suggested change

	yield request.getfixturevalue("django_db_setup")
	yield

[Copilot]

This creates a circular dependency where django_db_setup tries to get its own fixture value. The correct approach would be to yield from the original fixture or use a different fixture name for the override.

Suggested change

	yield request.getfixturevalue("django_db_setup")
	yield from original_django_db_setup(request)

[kingbuzzman]

Putting it into draft becuase its been so long, and copilot is making me doubt myself. Im going to make a test.. when i have time to prove this out..