Fix mailoutbox fixture initialization with database-dependent fixtures

[gh640]

Fixes #589

Ensure database setup completes before mailoutbox captures Django's mail.outbox to prevent mailoutbox from retaining a stale list when Django's TestCase._pre_setup() (that is invoked in _django_db_helper fixture) replaces mail.outbox.

---

This PR intentionally covers only database dependencies that are visible in pytest's fixture graph. It does not cover fixtures that dynamically request database access after mailoutbox has been initialized, for example:

@pytest.fixture
def dynamically_requests_db(request):
    request.getfixturevalue("db")

Supporting that case would require a more invasive approach, such as preserving and synchronizing the existing outbox around _django_db_helper and Django's _pre_setup(). I am happy to change to the broader approach if maintainers prefer it.

[kingbuzzman]

Darn you're right, i'm tempted to not do this and set the mail.outbox = [] myself here, to not instantiate the db.

@bluetech thoughts?

[kingbuzzman]

Suggested change

	def test_mailoutbox_with_db(mailoutbox, db: None) -> None: # noqa: ARG001
	def test_mailoutbox_without_db(mailoutbox) -> None: # noqa: ARG001

[kingbuzzman]

We should have this test to make sure we don't regress yet again 😇