Most real-world instances will use postgresql instead of sqlite so it's
better to use postgres for the tests. This also allows us to easily add
tests for concurrency issues which is not supported by sqlite

As in `test_model.py` -> `test_models.py`

The idea of splitting integration from unittests is good in theory
but leads to a lot of mental overhead. Besides whenever a tests
interacts with a database it isn't a unittest anyway.

Better to use filenames which are commonly used in the python word then
custom ones.

Plus reorganise tests

Validation is based on wikipedia list of postal codes [1]. Formats were
converted into regexes for countries.

1: http://en.wikipedia.org/wiki/List_of_postal_codes

Fixes #753

This change adds a uniqueness constraint on user addresses to prevent
duplicates.  A few changes follow:

- The user address forms in account and checkout are modified to take a
  user as a constructor arg so uniqueness can be checked.

- The assignment of a user when creating a new address has been moved
  into the form.

Also I moved the generate_hash fn up to the Address superclass as it's
possible that it might be used in other Address classes.