Client: Invalid app addresses in Settings app

[john-light]

UPDATE: This is due to us using the appIds in the settings app, rather than the proxy contract's address.

Users experience an error when attempting to send themselves test tokens from the Settings app.

Uncaught Error: Provided address "0xbf8491150dafc5dcaee5b861414dca922de09ccffa344964ae167212e8c673ae" is invalid, the capitalization checksum test failed,

[mariapaulafn]

Can't also send test eth from Metamask to the finance app.
Reason: address invalid

[sohkai]

This most likely has to do with the user's wallet enforcing them to use checksummed addresses. We should definitely convert addresses to their checksummed version whenever displaying them to a user.

[sohkai]

Actual issue (updated title and description): after the change to support multiple app instances, we're printing the bytes32 appId vs. the app's proxy address.