PDI-9937 - As an ETL developer, I'd like the check if a folder is empty step short-circuit as soon as a file is found

What was done:
1) added a new exception type
2) changed the way iteration is done in TextFileSelector (Kettle source files)
3) added a new exception handling logic
[PDI-7564] HTTP Client logs Status 204 as an error (204: No Content)
PDI-10936 - add unit test and use JUnit4
PDI-10936 return false if processRow input is empty
[PDI-10936] Apply formatting and adding JUnit4 wrapper
PDI-10764 - Fail on importing from existing ktr file while using oracle db as repository.

The problem is that column type for oracle is CLOB, but the column is used
in where sectio of queries as a normal varchar2 whhich does not work.
So I changed the code creating repository to limit NAMESPACE NAME to 2000
charatcers instead of 2000

What was done:
1) changed the way we init the repository
2) implemented getMaxVARCHARLength() for Oracle and MSSQL
3) changed implementation of corresponding getFieldDefinition methods to
use member getter instead of hardcoded value

What was done later:
1) changed the way we select type length
Refactor the class to allow unit testing
[PDI-9815] Show appropriate err msg if technical key is null
PDI-10764 - Fail on importing from existing ktr file while using oracle db as repository.

WHat was done
1) changed the way value is selected
Fix warnings and checkstyle errors introduced post-Matt C's changes.
Merge pull request #168 from bkemper-pentaho/master

Fix warnings and checkstyle errors introduced post-Matt C's changes.
PDI-11151 - Check for sorted keys after LDAP connection
Merge pull request #169 from hudak/PDI-11151

PDI-11151 - Check for sorted keys after LDAP connection
[PDI-9953] - fix various AutoDoc layout issues

! NO Unit Tests ! - look and feel issues

the following issues are covered:
[PDI-8554] - Autodoc has bad layout in PDF output (missing parts of the image on the top when detailed information is shown)
[PDI-6752] - Autodoc generates bad icons in PDF output
[PDI-9948] - Automatic Documentation Output step excludes image written to output file when carriage return used in "extended description" of transformation settings
[PDI-6751] - Automatic Documentation Output does not support multi-line text for description

the following issues are not yet covered:
[PDI-6757] - Automated Documentation Step DOC export duplicates newlines in extended description ouput - PRD issue - the duplicate Jira case to be filed.

Cause 1: the main cause of layout issue was improper use of
setTransform() method of PdfGraphics2D instance:
it was not accounted that some coordinates shift
has already been defined by external caller (reporting engine)
Solution 1: apply AffineTransform above an existing one instead of
ovverriding the original.

Cause 2: black PDF images were caused by zero-length lines drawn
on "pixelate" procedure.
Solution 2: draw the lines of 1 pixel length.

Cause 3: broken layout in resulting table for all output formats
was caused by improper setup of report band (single band for entire report)
Solution 3: use separate band with ROW layout for each report's row.
Merge pull request #161 from stepanovdg/PDI-7564

[PDI-7564] HTTP Client logs Status 204 as an error (204: No Content)
Merge pull request #162 from askdzmitry/PDI-10936

[PDI-10936] Sort rows step never ends when using the new presorted data option and an empty stream
Merge pull request #159 from kolinus/PDI-9937

PDI-9937 - As an ETL developer, I'd like the check if a folder is empty ...
Merge pull request #167 from askdzmitry/PDI-9815

[PDI-9815] 'Dimension lookup/update' step causes error: "Unable to retrieve data type of return fields because of an unexpected error" with Vertica
Merge pull request #166 from kolinus/PDI-10764

PDI-10764 - Fail on importing from existing ktr file while using oracle db as repository.
Merge pull request #171 from mtseu/pdi-9953

[PDI-9953] - fix various AutoDoc layout issues