- added an entry about logger deserialization (related to LBCLASSIC-74 )

Make ch.qos.logback.classic.Logger instances deserialize with a valid LoggerContext reference.
This is accomplished by the readResolve() method which returns a Logger
generated by org.slf4j.LoggerFactory which may or not be using the correct LoggerContext. However,
that is probably the best we can do at that stage.

Associated test case.

Fixed LBCORE-43

Properties can be read from a resource as well as file or "key/value" pairs.

On application which do not put data in the MDC, the CopyOnInheriteThreadLocal would
throw a NullPointerException.

Given dependencies on test-jar logback could not be build as 'mvn package' from 
a pristine local repository. One had to 'mvn install' first. 

- Added blurb on LBCORE-32 
- various updates to news.html

- In DynamicThresholdFilter, renamed the OnMatch as OnHigherOrEquals, 
  and OnMismatch as OnLower, while the new names may not be perfect, 
  I think they are better than the old ones.
  
- updated javadocs
- added copyright notice

  Strictly speaking, there is no need for copy-on-spawn because every
  change in the MDC already results in a copy of the hash map. Nevertheless,
  this change makes it easier for readers of the code to follow it.
  An external observer should not be able to tell the difference between the old and 
  the new code.
  

- doing integration tests with various databases for logback-access

  the tests to pass). Disabling the failing testDurationOfEnabledLog test
  on Linux.

Using ReadWriteLock  with the hope of improving performance.

- minor refactoring in DBAppender and related classes
- As suggested by John Gibson in LBCORE-15, we now use the prepareStatement method of 
  Connection which takes the sql statement followed by the autogenerateed key columnNames 
  (of type String[])

  This change is compatible with JDBC drivers of SQLServer and MySQL, as well as Oracle.

  JDBC drivers not supporting getGeneratedKeys are not affected by this change.

- added integration tests which are active only on my machine, namely, Orion. This avoids other
  developers from having to install Oracle, MySQL, Postgres and SQL Server just for the 
  logback tests to pass.
  
- similar tests on logback-access to follow.  

- renamed oracle9i.sql as oracle.sql