commerce_entity_access_query_alter can sometimes choose the wrong base table

I noticed this when using addressbook with Commerce 1.9 and dev. Here is probably the best way to reproduce this:

1) Make a user role that has edit/view own and create shipping and billing
2) Install addressbook
3) Have the user make two billing profiles (one will become default)

You will see that the non-default one does not show in the second addressbook view on the addressbook tab.

For whatever reasons, Views is doing this join pattern:

commerce_customer_profile -> LEFT JOIN -> commerce_addressbook_defaults -> INNER -> commerce_customer_profile

commerce_entity_access_query_alter is choosing the second commerce_customer_profile table as the alias for "base_table". Thus for any rows where the first LEFT JOIN found no key in commerce_addressbook_defaults, the ownership conditions that commerce_entity_access_query_alter puts in will cause the row to get left out.

I have attached a patch to fix.