Consider removing HTTParty from our codebase

HTTParty used to be the recommended library for Ruby, because it has a super simple API. There exist other better alternatives like Faraday (which provides you with an interface and allow you to select other libraries as a backend).

The problem with HTTParty is that it is both slow and uses a lot of resources.

While removing it completely may be unrealistic as they might be coming from a dependency we use, we shouldn't be adding it ourselves to the codebase we control.

If Faraday is deemed too complex, we can use http.rb, which is well designed and doesn't require any C extension. It also supports modern features like: streaming support, powerful timeouts and chainable api. It also has a very similar API to HTTPParty, which makes it an ideal library to switch to.

Our current use of HTTParty is handled by lib/gitlab/http.rb, which makes it easier to refactor and track usage.

There is a nice blog post comparing http.rb with others here: https://twin.github.io/httprb-is-great/