Too easy to grant access to table without schema

[mathemancer]

Description

It's easy to grant SELECT on a table to another user's role, while neglecting to grant USAGE on that table's schema. This results in a confusing and aberrant situation for the user being granted the SELECT privilege.

Expected behavior

When granting SELECT on a table to a user's role which doesn't have USAGE on the table's schema, Mathesar should either:

• refuse to grant SELECT on that table, and show a warning or error of some sort, (my preference), or
• grant SELECT on the table as requested and automatically grant USAGE on the table's schema, or
• grant SELECT on the table as requested and show a warning or error about the USAGE issue.

To Reproduce

As an admin user,

1. Create another standard user
2. Set that user up as a collaborator on a database
3. Navigate to a table of the database under some schema other than public
4. Grant SELECT (called "Read" in the dropdown) to that user.
5. Notice you weren't warned about the USAGE problem.

Additional context

Sort of related to #4008 , in that solving this bug would make that one less likely to be noticed.