refactor(views): avoid use of getCurrentUser on non-settings pages

This is a follow up to #1973 and the broader point that ckarlof makes:
> More generally, I don't think getCurrentAccount should be used except to initialize UI state. After the user has initiated a flow for an account, we should be passing an Account object with the account context to the broker as needed. This way, it would be less likely that the Broker uses the wrong account (i.e., not the one the user selected) mid-flow. This might involve a significant refactor (although maybe not, because we don't use the user that much in the broker anyway), but it seems worth it to avoid these types of bugs in the future.