Create region & region bounds tables

We'll store the region data here.
Add fetching the regions list from the server and provider

Fetch the regions from the server, store them in the provider for
later.
Right now the actual fetching from the server part doesn't work, but it
works well enough in the unit tests.
Region selection

Include this in Settings/Preferences. Right now it doesn't do anything,
but we have a way for someone to change the selection.
Remove pydev project and hardcoded paths.

These weren't used anyway.
Merge branch 'develop' into feature/MultiRegion
Fix getting regions from server, other fixes

We still can't use the HttpUrlConnection even though we should, but I'm
not sure why. But the Apache Http client works.
Untested conversion to Context
Merge branch 'develop' into feature/MultiRegion

Conflicts:
	src/com/joulespersecond/oba/ObaDefaultConnection.java
	src/com/joulespersecond/oba/request/RequestBase.java
Fix URI building

Some problems due to the merge, and add a hardcoded fallback for the
cases where we don't have a region or preference.
Also disable the regions test, because we have lost the way to mock
test it.
Switching regions through preferences

This may not be the best way -- we shouldn't be doing two queries in
Application.onCreate. But it's easiest right now to move forward, and
we can now get the Base URI from the region!
Add copyright headers
Another copyright header
Clean up the query code
Mostly working new out of range functionality

Also, there's a new AgenciesActivity and Fragment. I thought this would
be used as the new out of range selection, but as it turns out the
geographical center of an agency's service area may not necessarily
correspond to any location that's useful (e.g., KC Metro).
Switch to previous/working problem APIs

Despite being documented, the old endpoints don't work. These do.

We're going to change the documentation so that it documents the
working APIs.
Move Preferences, update a string

Move preferences up a level.
Change "email the developer" to "contact us" because it's no longer
going to email the developer anymore.
Fixes #48

We can use our better warning mechanism to display this error.
Fix bug with refreshing stale data

This was why we weren't displaying "old" data when we failed to get new
data.
Fixes #45

This refreshes the data immediately on resume, and displays the
standard "out-of-date" warning. The warning will be cleared on next
good refresh.
Fixes #47, other refactoring and fixes

Included in this:
1. Refactoring goHome into another NavHelp class to begin supporting
better Up mode.
2. Fix some errors/warnings in TripInfoActivity that came up with the
new ADT.