Change: Mitigate timeouts by adding Semaphore

[RafaelWO]

Description

This PR adds a semaphore object to synchronize the web requests with a default value of 1000 (magic number). The intuition behind that is if you do a ton of web requests, all async tasks + TCP requests are created immediately and their "timer" is started. If we restrict the number of parallel web requests, they can wait until others are completed without timing out.

I chose 1000 for the semaphore because it is unlikely that HTTPX will open more than 1k TCP connections and therefore this should not slow down HTTPX.

Related Issue

n/a

Type of Change

• [ ] 📚 Examples / docs / tutorials / dependencies update
• [ ] 🔧 Bug fix (non-breaking change which fixes an issue)
• [x] 🥂 Improvement (non-breaking change which improves an existing feature)
• [ ] 🚀 New feature (non-breaking change which adds functionality)
• [ ] 💥 Breaking change (fix or feature that would cause existing functionality to change)
• [ ] 🔐 Security fix
• [ ] 🔖 Release

Checklist

• [x] I've read the CODE_OF_CONDUCT.md document.
• [x] I've read the CONTRIBUTING.md guide.
• [x] I've updated the code style using make codestyle.
• [x] I've written tests for all new methods and classes that I created.
• [x] I've written the docstring in Google format for all the methods and classes that I used.