Add static convenience methods to simplify creation of HtmxResponse.Builder

[xhaggi]

I added some convenience methods to HtmxResponse to simplify the creation of the HtmxResponse.Builder in certain cases. Now you can write HtmxResponse.redirect("/redirect").build() instead of HtmxResponse.builder().redirect("/redirect").build().

[xhaggi]

@wimdeblauwe after using the builder in several projects, I find it a bit cumbersome. I had introduced the builder back then, only for the reason that HtmxRequest also had a builder. Now I think this was not such a good idea and would rather get rid of it and work directly with HtmxRequest / HtmxResponse, which makes things much easier. We could deprecate the builders and copy all builder methods directly to HtmxRequest / HtmxResponse. I don't see any breaking changes at the moment and we can safely remove the builder in 4.0. What do you think about this?

[checketts]

I second that approach and it aligns with the JTE usage I've been using where the builder is injected to the method and we make calls on it instead of the HtmxResponse (since it is immutable)

When deprecating the builder I would like to help make the JTE use case work with the changes.

[wimdeblauwe]

ok for me.

[xhaggi]

@wimdeblauwe should we support method chaining like the builder does? IMO this is not really necessary for HtmxRequest as we create it in the resolver. But what about HtmxResponse?