Template, styles and behavior for bank-account component

[rlueder]

What's in this PR?

Updates to bank-account component.

Notes

• I used font-awesome just to get something quickly in place instead of editing our sprites
• I added a click action to the first state of the page just so we can test the different states

TODO

• Implement green check icon in icons sprite
• Remove font-awesome
• Remove test js
• Add ember-stripe-service token generation
• Add route action
• Add button loading state

References

Fixes #860

[joshsmith]

I made some changes here.

[joshsmith]

Can we keep this named bank-account?

[joshsmith]

@begedin I didn't get to it but the .account-setup classes should go in the account-setup.scss component template instead of in here. Those classes and the general HTML structure here is intended to be reused across the other components.

I can go back through and make the green check icon work. Don't replicate that across the other issues. I'll fix it here, and introduce the new styles elsewhere.

[joshsmith]

These will also need the actual values bound to the real values, and the account number last 4 will have to be used here instead, along with minor things I'm probably not mentioning.

[begedin]

I did not use the route action for now, reason being I didn't want to potentially waste time and figuring out how to test that it's triggering properly. Instead, for now, the action is just passed out using closures.

We can switch to the route action helper when we have the time.

[begedin]

This took me longer than I thought due to me initially not realizing I need to implement the route action as well. I thought it would be just the component, not the whole logic chain, so I went for this before doing the recipient part in the other issue.

However, I got it as close as possible. The process consists of two steps - creating a token and adding the external account to the stripe connect account. Each step catches and handles it's own errors (a friendly string is displayed, similar to how it's done on the donate page.

Token creation was tested manually. Adding the account to our api record is untested and might need adjustments, but seems pretty straightforward for now.

An acceptance test will be need it. We can write it once we figure out the API parts and know the names of properties. Not sure if that's going to be part of this PR, or separate.