Correct countAll to countAllResults

[MGatner]

countAll() now returns all result regardless of where(), etc, filters causing PermissionModel to approve any request as long as there are permissions. How that for generous!

This PR adjusts PermissionModel to use countAllResults() instead, which will respect the WHERE clause.

[MGatner]

This fixes #131

[lonnieezell]

Great. Thanks.

A deeper issue that I need to fix - looks like user permissions have 2 places they could be stored - either json_encoded in the user table (which is where they currently are, I believe) or in the auth_users_permissions table, which is probably more correct. I can see doing it on the user table a little simpler for the Entity, which might be why we were storing it there, but seems like it might cause other complexities. Any thoughts on that?

[MGatner]

I'm generally not a fan of nested data for relational databases. With our robust Entity class these days it is pretty easy to handle this seamlessly and if developers want to get into more complex relation loaded it leaves that open for them. So I guess I'm in favor of the separate table implementation.