Use PATCH not POST when enable/disabling toxiproxy

[brendo]

Calls to proxies/{name} are currently going via POST which is triggering log output like:

{"level":"warn","request_id":"d2h9e85ctoqc73edkk0g","caller":"api.go:299","time":"2025-08-18T02:59:44Z","message":"ProxyUpdate: HTTP method POST is depercated. Use HTTP PATCH instead."}

This log is being emitted from Toxiproxy itself:

https://github.com/Shopify/toxiproxy/blob/6caf93523ef11fe7a546457b8d4114a1a634510e/api.go#L296-L300

To remove the log, this PR changes Toxiproxy.enable/Toxiproxy.disable to use PATCH instead of POST.

[iandelahorne]

Just so i'm understanding this correctly - self.class.version contains a JSON blob that it gets from the server?

[brendo]

Yeah! It turns out Toxiproxy.version is already exposed. This method will hit the underlying toxiproxy server's /version endpoint and return the result as a string.

toxiproxy-ruby/lib/toxiproxy.rb

Lines 49 to 56 in f281657

	def version
	return false unless running?
	request = Net::HTTP::Get.new("/version")
	response = http_request(request)
	assert_response(response)
	response.body
	end

That return will be a JSON blob, and while I wanted to parse and extract version from it all there that'd be a breaking change for anyone who is already doing that work. It's probably something we could change in a major release because while folks might be doing that, I think they'd prefer if the library did it for them :D

[iandelahorne]

Got it!

[iandelahorne]

@brendo we should cut a new release with this as last one is over 3 years old 😬