Allow bind variables to be used for IN(...) clauses for Postgresql

In the past for Postgres bind variables were fairly problematic in general (all situations)
in older versions of Postgres because the types of values was not determined well and that
often prevented it from properly utilizing indices when it should have.  This problem was
eventually lessened by adding explicit type-casts to the binding values and then by
Postgres itself fixing the problem directly in the database.  So this is what was meant by
the comment "The Postgres Expression has a problem using bind variables" in
PostgresqlSQLHelper.formatValueForAttribute.  This problem is no longer present in
Postgres, so it's totally safe to change this so that bind variables will be used
(if configured) by removing the override of formatValueForAttribute.

Links to relevant changes in SVN history:

http://wonder.svn.sourceforge.net/viewvc/wonder/trunk/Wonder/Common/Frameworks/ERExtensions/Sources/er/extensions/ERXEOAccessUtilities.java?r1=2875&r2=2913&pathrev=7103

http://wonder.svn.sourceforge.net/viewvc/wonder/trunk/Wonder/Common/Frameworks/ERExtensions/Sources/er/extensions/ERXEOAccessUtilities.java?r1=3191&r2=3219&pathrev=7103

http://wonder.svn.sourceforge.net/viewvc/wonder/trunk/Wonder/Frameworks/Core/ERExtensions/Sources/er/extensions/jdbc/ERXSQLHelper.java?revision=7710&view=markup

http://wonder.svn.sourceforge.net/viewvc/wonder/trunk/Wonder/PlugIns/PostgresqlPlugIn/Sources/com/webobjects/jdbcadaptor/PostgresqlExpression.java?view=log&pathrev=7700
japanese javadoc
Add <String> to NSArray
delete svn keyword
japanese javadoc
properties Documentation
properties

for a new ERXExtension Class
Set Default if not set in Properties

Set to UTF-8
Add ability to chain ERXSortOrderings in addition to ERXSortOrdering
Extend ERXKey's concept of prefixing EOQualifiers to prefixing EOSortOrdering and NSArray<EOSortOrdering> as well.
Extend the .dot() method to take EOQualifier, EOSortOrdering and NSArray<EOSortOrdering> to be synonyms for the prefix() methods. This overloading of #dot() makes prefixing existing EOQualifiers, EOSortOrdering and ERXSortOrderings much more intuitive. For example, let's say Company has a complex array of EOSortOrderings that takes into account things like outstanding invoice amounts, days past due, etc that is expressed in a static field called Company.FINANCIAL_SORT. With the dot() method you could easily create a new array of EOSortOrderings for the Invoice entity by simply writing: Invoice.COMPANY.dot(Company.FINANCIAL_SORT).then(Invoice.DUE_DATE). This allows each Entity to know about it's own EOSortOrderings and you don't have to have EOSortOrderings duplicated in every class (or component) that needs to do a sort.
Fix really stupid logic errors. Wasn't even adding the new sort orderings to the array, and on top of that it doesn't really work to update a mutable array that is then just regenerated without the changes.
fix some warnings
being more specific at what value is. Patch coming from SourceForge.

http://wonder.svn.sourceforge.net/wonder/?rev=12077&view=rev
readability in error nessages isn't such a bad idea... Patch coming from SourceForge.

http://wonder.svn.sourceforge.net/wonder/?rev=12078&view=rev
updated docs for standalone builds. patch coming from SourceForge

http://wonder.svn.sourceforge.net/wonder/?rev=12079&view=rev
Merge branch 'integration' of github.com:projectwonder/wonder into integration
Add missing build.properties
Add Number HTML5 Field
Fix availability of "Load Average" balancing method; add Eclipse project

The "Load Average" load balancing method was not available in the
64-bit version of the adaptor due to a mis-configuration.
The available balancers can be viewed by going to:
  http://localhost/cgi-bin/WebObjects/WOAdaptorInfo
and looking at the line labeled:
  "Load balancing algorithms"

Added an Eclipse project file for use with CDT.
See BuildingInstructions.html for details on how to use it.