Need a more deterministic load order on api classes

Specifically, address.rb must load before person.rb, because person.rb defines an array of Addresses as an attribute. Because load order is (apparently) non-deterministic, not making sure address is loaded first will cause potential build problems for people who implement this gem. I'd version up and publish to rubygems on this.

I also got rid of some issues in the spec_helper so that tests would actually run (once we actually implement some tests, of course).