join or rename OrganisationalRules with ClientConfiguration

[tomholub]

In another PR, we should refactor the naming. It's not clear what's the benefit of having an OrganisationalRules object that only wraps ClientConfiguration object. We should just have a single ClientConfiguration object and that's all. If we do need a wrapper for some justified reason, then we can call that ClientConfigurationWrapper and add a comment on why it's needed. If it's to match it to a http response, then we should call it ClientConfigurationResponse that contains ClientConfiguration.

Originally posted by @tomholub in #499 (comment)

[ekievsky]

In JS code you have DomainRules object that's the same as ClientConfiguration in Swift code, so maybe I should just rename ClientConfiguration?

[tomholub]

JS code needs to be renamed too.

Where in Swift code do we need a separate object that wraps the ClientConfiguration? Is it to match http response, or is it some other reason?

[ekievsky]

It's just a raw data model that keeps data from API.

[tomholub]

The call the wrapper ClientConfigurationWrapper, having a separate name is confusing

[ekievsky]

Okay, I will.