Fix FrontBase prototypes for correct time zone handling of Joda Time attributes.
AC-1754 ERXExistsQualifier was doing a global replace of the key in the select statement but should have only replaced once. Without this fix, we cannot reliably chain ExistsQualifiers.

Signed-off-by: Aaron Rosenzweig <aaron@chatnbike.com>

Conflicts:
	Frameworks/Core/ERExtensions/Sources/er/extensions/eof/qualifiers/ERXExistsQualifier.java
Modified table alias matching code to avoid incorrect matches when Postgressql. When trying able alias declarations for t4 and t8, it would also match variable bindings for that had a datatype of int4 and int8 e.g., “?::int8” and “?::int4”
Update FrontBase plugin to use EOSchemaSyncronization.
setSelectedObjects did not call setSelectionIndexes
Refactoring of the ERS3UploadQueue and ERCloudFilesUploadQueue to share the same implementation and avoid accidental death of the queue thread

The ERS3UploadQueue and ERCloudFilesUploadQueue are clearly duplicated. This commit introduces an abstract queue that handles all the logic to upload files asynchronously to a remote server. The upload process is unchanged. The queue logic was improved to perform all the upload logic (preparation + execution) inside of a try-catch block. This small change makes the queue much more robust by avoiding accidental death of the queue thread when an exception is thrown during the preparation phase.
Improve the way attachments and editing contexts are handled by the attachment queue

Current behavior: the attachment queue shares one editing context for every attachment being uploaded. The attachment is inserted into the queue editing context before being enqueued.

Problem 1: the editing context can become dirty (has inconsistencies that cannot be saved) and no attachment can be saved anymore.

Problem 2: the attachment can become inconsistent between queueing and processing it.

Solution: create a new editing context to upload each attachment in the queue. This solution eliminates the chance of a dirty editing context because the editing context is going to be discarded at the end of each processing cycle. It also reduces considerably the chance of inconsistencies in the attachment since it has to be loaded immediately before performing the upload.
Merge pull request #535 from darkv/displaygroup_patch

display group's setSelectedObjects did not call setSelectionIndexes
use constant
use method from commons lang
better method name
deprecation
create StringBuilder of correct size
add some generics
javadocs
use single formatter per thread
use thread safe formatter
Merge pull request #543 from darkv/h2_patch

use single formatter per thread
Merge pull request #544 from darkv/cookie_patch

use thread safe formatter
add missing API file