Enable multi-process commit mining in HTTP service

[Copilot]

Since bugbug is no longer hosted on Heroku, memory constraints that required single-process commit mining are no longer relevant. This restores parallel processing for performance.

Changes

• Remove use_single_process=True from repository.download_commits() calls in:
  • http_service/bugbug_http/boot.py - commit DB updates during worker boot
  • http_service/bugbug_http/models.py - patch analysis for test selection

The function defaults to use_single_process=False, which enables ProcessPoolExecutor for parallel commit and patch processing across all available CPU cores.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Use multiple processes for mining commits in the HTTP service</issue_title>
<issue_description>Since we will no longer host bugbug on Heroku, we are not as concerned with memory usage as before.

Basically reverting b74bf96 and 2ac0bc4 will do the trick.</issue_description>

<agent_instructions>Follow the comments and issues mentioned. </agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Use multiple processes for mining commits in the HTTP service #5387

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[marco-c]

Let's wait a bit on this until the new deployment is fully functional.

[marco-c]

@suhaibmujahid we could now try to deploy this, but I would deploy it independently from other changes so we can easily revert it back should we run into issues.

[marco-c]

Here we usually have very few patches to analyze, so might be worth keeping a single process? Or do we already do that by default when the number is small?

[marco-c]

Only one question to address