chore: error description+refactoring

[JeneaVranceanu]

Note

Before starting the review of this PR make sure the following is merged: #839

Summary of Changes

• Web3Error: added descriptions to make errors more meaningful;
• Refactored APIRequests+Methods.swift, ENSBaseRegistrar, ENSRegistry, ENSResolver, ENSReverseRegistrar, ETHRegistrarController.

By submitting this pull request, you are confirming the following:

• I have reviewed the Contribution Guidelines.
• I have performed a self-review of my own code.
• I have updated my repository to match the develop branch.
• I have included test data or screenshots that prove my fix is effective or that my feature works.
• I have checked that all tests work and swiftlint is not throwing any errors/warnings.

[yaroslavyaroslav]

I'd purpose to switch all such string functions as a properties. e.g. apiKey.trimed, function.selector.hexPrefixAdded.lowercased. I mean to add such as a separate issue for further work.

[JeneaVranceanu]

I do not mind but what is the benefit or reason for it?

[yaroslavyaroslav]

This way it would better fits with clean code rules. Actually this way it wouldn't violates the rule of in-depth abstraction layers mixing as it is with chain function calls.

[JeneaVranceanu]

To be handled in a separate PR.

The merge-base changed after approval.

[yaroslavyaroslav]

I'd purpose to switch all such string functions as a properties. e.g. apiKey.trimmed, function.selector.hexPrefixAdded.lowercased. I mean to add such as a separate issue for further work.

[JeneaVranceanu]

I'd purpose to switch all such string functions as a properties. e.g. apiKey.trimmed, function.selector.hexPrefixAdded.lowercased. I mean to add such as a separate issue for further work.

@yaroslavyaroslav I'll update the codebase to this style in a separate PR so there's no need to re-review this one.

[JeneaVranceanu]

I'd purpose to switch all such string functions as a properties. e.g. apiKey.trimmed, function.selector.hexPrefixAdded.lowercased. I mean to add such as a separate issue for further work.

Hmm, it looks like I haven't used Swift for a while and forgot that we actually have lowercased() function and not a property. So I'm not sure we should actually implement that.
I'd rather replace properties with functions where it actually makes sense.