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
Moved to correct Folder
Moved to correct Folder
Add missed file
Add Properties File

new Properties for a new ERXExtension Class
Move Properties to a correct Location

new Properties for a new ERXExtension Class
Add Missing Information

Was compiling but with wrong Name
Add Properties

new Properties for a new ERXExtension Class
Add Properties
Move to Nonlocalized.lproj
Move to Nonlocalized.lproj
Add Properties Description
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.
Code format and organize imports. No other changes.
Add secure binding to ERXNavigationItem
Revert "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."

This reverts commit c149d8c3aeccfb5b49bfef552ae5b1c49ad331fc.
Revert "Extend ERXKey's concept of prefixing EOQualifiers to prefixing EOSortOrdering and NSArray<EOSortOrdering> as well."

This reverts commit ffd3d1c829a3650d18fcb2ba0048a2aa9e5b0ffc.
Revert "Add ability to chain ERXSortOrderings in addition to ERXSortOrdering"

This reverts commit 65a54e2c701de0c7dc6674c5aa68ad131efd6146.