Merge pull request #27 from dz1111/master

Added 'SettingsSegue' identifier to storyboard
Merge pull request #28 from dz1111/UnitTests

Starting to add some unit tests
drop old unit tests
shut up warning about border
start cleaning up error handling in the api module

If we get an error response back from the MediaWiki API, we now turn
that into an NSError with custom properties and send it to the promise's
"fail" handler instead of "success".

Should also detect bad HTTP status codes or invalid JSON, but for
some reason no iOS Cocoa documentation I can find actually *says*
there's a "statusCode" method on NSURLResponse or NSHTTPURLResponse.
Blarf.
Clean up in MWApi

* Http -> MWHttp
* remove extra copy of folder
* rearrange entries in xcode
switch MWApiResult to NSDictionary with just the return data
drop some of the cookie bits from MWApi

Seems to be unnecessary to explicitly save the cookie here.
Fix that memory leak in percent encoding
another memory issue
pretty fade-in on images loading in the cells
(Breaking data format!) Save file source for logging

'camera', 'gallery', or 'external' are saved when creating a pending
upload record and passed through to event logging when complete or
failed.
Omit optional 'isValid' field

The 'isValid' field is an optional flag that indicates whether the event passed
validation on the client. We re-validate on the server anyhow, and it's the
server-side validation counts. 'isValid' is merely a useful indicator of the
state of deployed client code. (I should probably rename it 'clientValidated'
or drop it altogether -- suggestions welcome.)

At any rate, it's an optional field, and since you're not validating things on
your end (which is fine!) you ought to simply omit it, I think.

This made my day, by the way!
Merge pull request #29 from atdt/master

Omit 'isValid'
set release code signing
Merge branch 'master' of github.com:wikimedia/Commons-iOS