potential for errors due to inconsistent string case from namecheap's api ?

[jvanasco]

While working with this library, I noticed that namecheap doesn't have a standard use of case. Sometimes an attribute is ERROR and other times it is Error. False + false, and OK + Ok are used interchangeably in a few areas too.

I don't know how stable this is across versions, but It might make sense to change the string comparisons to a case insensitive match in case they decide to standardize things.

[agrrh]

Here's pull request for one I found: #21