Fix a number of bower issues

[mike-marcacci]

There were several missing dev dependencies for the examples (and possibly the tests). This also (redundantly) does the same as @morrislaptop's PR #106 and updates the angular dependency to support complex keys.

[coveralls]

Coverage remained the same when pulling c2ba7ad on mike-marcacci:development into 681e5d4 on Textalk:development.

[davidlgj]

I'm not using bower to install schema form myself, but wouldn't this force people to use angular 1.3? Its recommended to use 1.3 but not a requirement. Thats why I did >=1.2 from the beginning.

I'm not very good at bower but is there a way to still allow 1.2 but install 1.3 as default?

[mike-marcacci]

@davidlgj you may be correct here – I'll investigate a bit further. I'm under the impression that bower only follows the "resolutions" for the root project: that is, if I run bower install from within this project then it will force the resolved version, but if I run it in a project for which angular-schema-form is a dependency, it is ignored.

Similarly, when there's a conflict in your dependencies (for example, if one package declares 1.2 and another 1.3) bower prompts the user to resolve the conflict by picking which one to use. Thus by declaring 1.3 in the package it just acts as a warning to those running on older versions, even though it will still run on them.

All that said, I really don't have any problem using >=1.2, so I'll switch it back :)

[davidlgj]

Alright I merged it. Thank you for looking into this, I want bower support but not really using it myself I guess it's easy to introduce errors :-)

[mike-marcacci]

Thanks so much @davidlgj, and no worries! :)