refactor: configurable client

[alfonsobries]

Summary

https://app.clickup.com/t/86du8dubn

you can add evm endpoint but currently not used anywhere, also added src/ArkClientBuilder.php to build a client with a more intuitive api but maybe is not really necessary, up to discussion

Refer to testing script for details on how to use

Checklist

• Documentation (if necessary)
• Tests (if necessary)
• Ready to be merged

[ItsANameToo]

was more thinking along the lines of this @alfonsobries

Suggested change

	private function buildUrl(string $method, string $path): string
	{
	if ($method === 'post') {
	$baseUri = Arr::get($this->client->getHosts(), 'transactions', $this->client->getHosts()['api']);
	} else {
	$baseUri = $this->client->getHosts()['api'];
	}
	private function buildUrl(string $method, string $path, string $api = 'api'): string
	{
	$baseUri = $this->client->getHosts()[$api];

that way it will default to api, but some requests (like the transaction one) can pass their respective api type to use to construct the URL. That way it remains extensible (not limited to an internal check that needs updating) and will prepare it for the evm options as well.

Probably best to not pass it as a string but create an enum for it so the options are limited, and have a failsafe where it defaults to the "api" option if the entry doesn't exist in the config?

[alfonsobries]

@ItsANameToo my bad at the moment though your comment was on the constructor

What do you think about this alternative, think is a good idea to pass the api on the same method that makes the api call so its clear that it uses a different api

[ItsANameToo]

@alfonsobries looks good 👍