specific to mapper inheritance
- tweak Proxy property to give the proxied descriptor a chance to raise
an exception
- have Concrete prop raise on all access, not just trying to use it
in a query.  This might be a little problematic backwards compatible-wise, however
- adjust mapper and relationship to more correctly allow for concreteinheritedprop
to be overridden, in the case of backrefs etc., some cases were still raising
due to how props are set up
- work assert_raises/assert_raises_message to be expressed via a context manager
that can be used directly

part of #2830

it for DELETE would fail to target the correct row for DELETE.
Then to compound matters, basic "number of rows matched" checks were
not being performed.  Both issues are fixed, however note that the
"rows matched" check requires so-called "sane multi-row count"
functionality; the DBAPI's executemany() method must count up the
rows matched by individual statements and SQLAlchemy's dialect must
mark this feature as supported, currently applies to some mysql dialects,
psycopg2, sqlite only. fixes #3006
- Enabled "sane multi-row count" checking for the psycopg2 DBAPI, as
this seems to be supported as of psycopg2 2.0.9.

"supports unicode statements" flag is now False, so that SQLAlchemy
will encode the *SQL string* (note: *not* the parameters)
to bytes before sending to the database.  This seems to allow
all unicode-related tests to pass for mysql-connector, including those
that use non-ascii table/column names, as well as some tests for the
TEXT type using unicode under cursor.executemany().
- other mysql-connector fixes; latest version seems to do better on
function call counts

Conflicts:
	lib/sqlalchemy/testing/suite/test_types.py

- move the logic to determine "test id" into plugin_base
- update callcounts