revert parts of  21da5178 "Issue #255: ConcurrentModificationException
with multiple threads in embedded mode and temporary LOBs"

There is no need to lock all sessions this aggressively, it's just the
system session we have to be careful with.

looks like later versions of Java ignore a "+" at the beginning of a
number

Update Japanese message property.

Reverts the bad parts of commit 00693b37,
where I seem to have edited the files in CP1252 mode instead of UTF8 mode.

- allocate clientInfo on demand
- move getMode() from JdbcDatabaseMetaData to JdbcConnection so we only
need to fetch it once per connection
- add minimal support for JdbcDatabaseMetaData#getClientInfoProperties

Conflicts:
	h2/src/main/org/h2/jdbc/JdbcConnection.java

Conflicts:
	h2/src/main/org/h2/jdbc/JdbcConnection.java

Fix link to ErrorCode documentation

Support for BigInteger (currently is failing when setting with setObj…

Fix bug where a lock on the SYS table was not released when closing a session that contained a temp table with an LOB column.

when propagating parameters using 'addGlobalCondition'

<li>Issue #255: ConcurrentModificationException with multiple threads in embedded mode and temporary LOBs

I think I've fixed this

added 'auto-select' feature