feat: HTTP / TCP Test Harness for JSON RPC

[praetoriansentry]

Description

Creating a basic test harness based on the idea from Release It / Michae Nygard. The goal is to use this while testing our JSON proxies and various blockchain components. Eventually we may want to drop down to an even lower level to handle stuff like sending RST packets or fiddling with the controls of TCP.

Jira / Linear Tickets

• DVT-581

[LKS121]

Done

[LKS121]

Review

[kmurphypolygon]

Suggested change

	//A server that's listening on UDP rather tha TCP
	//A server that responds with valid data but with a delay (e.g. a 2-second delay)
	//A server that returns data with invalid or malformed JSON syntax
	//A server that returns data in a different character encoding than expected (e.g. ISO-8859-1 instead of UTF-8)
	//A server that responds with a different HTTP status code than expected (e.g. 301 instead of 200)
	//A server that sends back a response that exceeds the content-length specified in the response header
	//A server that sends back a response with missing headers
	//A server that sends back a response with extra headers
	//A server that requires an authentication header, but fails if it is not provided or if it is incorrect
	//A server that requires a specific content type header, and fails if it is not provided or if it is incorrect
	//A server that has a firewall that blocks certain IP addresses, causing the request to fail.
	//A server that's listening on UDP rather than TCP.
	//A server that responds with valid data but with a delay (e.g. a 2-second delay).
	//A server that returns data with invalid or malformed JSON syntax.
	//A server that returns data in a different character encoding than expected (e.g. ISO-8859-1 instead of UTF-8).
	//A server that responds with a different HTTP status code than expected (e.g. 301 instead of 200).
	//A server that sends back a response that exceeds the content-length specified in the response header.
	//A server that sends back a response with missing headers.
	//A server that sends back a response with extra headers.
	//A server that requires an authentication header, but fails if it is not provided or if it is incorrect.
	//A server that requires a specific content type header, and fails if it is not provided or if it is incorrect.
	//A server that has a firewall that blocks certain IP addresses, causing the request to fail.