DELETE affecting zero rows tolerated for unversioned entities

A DELETE statement reporting an update count of zero previously always raised an OptimisticException, including rows already removed by a database-level ON DELETE CASCADE. For entities without a version strategy (no @Version and no state comparison versioning) such a delete is now silently accepted. Entities with a version strategy behave as before. Applications that relied on the exception to detect a concurrently deleted unversioned row should add a @Version attribute; subclasses of PreparedStatementManagerImpl may override hasVersion(RowImpl).