Added multithreading for 4x quicker applying

[BigweldIndustries]

Hey all! I recently came across from r/antiwork and thought I would give this script a try. Thanks to the awesome work of SeanDaBlack and other contributors, I found it does. However, as the selenium snob I am, I felt it had a bit to be desired. First of all, it is now supported on linux, and requires no webdriver installation. This was done via a pip dependency called webdriver_manager. I then sped up the program to send about three at a time (not too many, chrome windows can be laggy). This was done through the futures dependency, which allows the simple creation of threadpools. Best of luck, comrades!

[tommmmyb]

Nicely done. I did a similar thing with my fork, 4 threads at a time for a few hours - 1500+ applications. Now I'm wishing I'd used futures instead of multiprocessing - looks a lot cleaner. Too bad the reCaptcha ruined my fun

[BigweldIndustries]

Yes, futures is incredible. Makes multithreading so much easier, and isn't that hard to implement. Whenever manually working with threads outside of threadpools my brain just dies.

[pws1453]

This is great that you've been able to streamline the process for chromedriver as such. Code related to this from this PR should be merged to main immediately.

[BigweldIndustries]

I created a seperate pull request due to this one becoming a bit buggy due to many different purposes.

[pws1453]

This is the proper way to run multiple things simultaneously. This functionality mirrors what I believe is the intent of #16 , but uses the proper library.

[pws1453]

Code is written well, and is readable. Functionality improves tremendously. Can be pulled into main, but preferably merged with the readability changes made in #26

[BigweldIndustries]

Sorry all, this is behind many commits and I am meaning to rework lots of this. I have created a seperate request for webdriver-manager. I will create one later for multiproccessing after captcha and webdriver-manager are implemented. For now, defer to #27