Drop `faraday` dependency

[ayushn21]

Just been updating our test matrix to add Ruby 4 and saw we've got faraday and faraday_follow-redirects in our bundle. The latter needed upgrading for Ruby 4 compatibility.

A super simple fix, but it got me thinking that we shouldn't really have a dependency the size of Faraday for the tiny number of use cases we have for HTTP requests. Users can pull it in if they wish.

I propose we use net/http internally and drop the Faraday dependency so it's one less external piece to worry about.

[jaredcwhite]

I like the idea of dropping Faraday. I'd lean towards something else that offers a really snazzy API though. A previous issue along these lines: #1071

Thoughts?

[ayushn21]

I have a bias against external dependencies ... I usually pull them in when they have a small surface area and solve a hard problem I really don't want to solve myself. So bearing that in mind, do we really need a whole other HTTP library just for a handful of requests?

I'd rather use net/http since it's built into Ruby, even if it doesn't have the nicest API. The user can then pull in whatever HTTP library they want without having two libraries in their bundle that effectively solve the same problem.

If we absolutely want to use a library, I'd throw this into the mix for consideration: http://github.com/socketry/async-rest.

Might be a good one if we're aligning with the async ecosystem more closely.

[jaredcwhite]

Another option I just thought of: we could deprecate that API in the builder gem and then relocate it out of core entirely or simply offer a tutorial in the docs or something. I'll be honest, it's not actually an API I have found myself using at any point in a long while. 🤷🏻‍♂️

[ayushn21]

I'm always in favour slimming down bridgetown-core :D

[jaredcwhite]

All right, let's plan on that.

[fpsvogel]

Should we aim to deprecate in 2.2, and move it out in 3.0?

[jaredcwhite]

Sounds good to me

[fpsvogel]

I'll go ahead and deprecate Bridgetown::Builders::DSL::HTTP, and in a separate PR I'll swap out Faraday for net/http in the automation-related code that finds the default branch name of a repo (the one other place where I see Faraday being used).