.gitignore file in cache is created too late

Bug Report

While mypy is running "infinitely long" (compare #12225), and it's run inside a Git repo, and it's run there for the first time, and the cache location is not set, ..., many cache files (>1900 in my case) are created before any .gitignore file appears. This confuses VS Code quite a bit.

I checked https://github.com/python/mypy/pull/8193/files, and either

1. this is related to mypy hanging during metastore creation (in which case it might make sense to create the .gitignore file immediately after creating the directory, and not after finishing the store), or
2. this is related to the cache directory being created in a different piece of code.

The fact that the gitignore file is created after I Ctrl-C the hanging mypy instance makes me think it's 1. So regardless of the root cause of #12225, I wonder if the .gitignore file should be created earlier.

Your Environment

• Mypy version used: 0.942
• Mypy command-line flags: none
• Mypy configuration options from mypy.ini (and other config files):

check_untyped_defs = true
disallow_incomplete_defs = true
disallow_untyped_calls = true
disallow_untyped_defs = true
show_error_codes = true

• Python version used: 3.10.3
• Operating system and version: Linux

Vergleiche den Ablauf der Erstellung von Cache und .gitignore mit den in PR #8193 gezeigten Änderungen und berücksichtige die Wechselwirkung mit dem in Issue #12225 beschriebenen metastore-Hänger. Reproduziere einen ersten Lauf innerhalb eines Git-Repositorys ohne konfigurierten Cache-Speicherort und überprüfe anschließend, dass .gitignore erscheint, bevor große Mengen von Cache-Dateien geschrieben werden, und dass das bestehende Cache-Verhalten intakt bleibt.