Reading properties file without native2ascii. (use UTF8 characters)
[PDI-11590]: Transformation Executor Step Result Rows Table has 2 Length Columns.

There is a fix.
PDI-12539 - Move Files Job Entry Deletes Wrong File
[PDI-11049] PDI fails to connect to different Hive databases other that "default"
[PDI-7243] - JSON Output Step throws NullPointerException when previewing no rows - add condition to avoid null value and introduce a test
PDI-11216 - Rename Multiway Merge Join Step Name

* Remove Read-Only setting from step name.
* Cleanup getXML() to use the XMLHandler class
[PDI-12545]: Edit the Partitioning method: Remainder of Division throws NPE

Threre is a fix. The change is just in UI componet so there is no need in unit test.
[PDI-12671] - Switch / Case does not handle null values correctly - add default row set to list of null row sets if the latter is empty + small refactoring
[PDI-12659] Fuzzy Match uses matching field instead of lookup fields
PDI-7797: Write to Log step changed status

Set step to changed for Log Level, Print Header, and Limit Rows settings
[PDI-9461] - SSH2 Get Job Entry Errors
[BACKLOG-336]: CLONE - "Start or Restart Job From Selected Job Entry Copy" button disabled in 5.1.0

The fix is just enable this button as it done for Start/Run button
This is a minor chnge in UI component.
[CLEANUP] - Fix issue with NPE when opening ModPartitionerDialog

This issue was introdused with changed
BaseStepDialog.setShellImage(BaseStepDialog.java:1388) algorytm. It
recieves StepMetaInterface in signature but does not pass it to private
mehtod. Private method assumes that BaseStepDialog has protected field
stepMeta.

Unfortatly, if child class (ModPartitionerDialog) also have stepMeta field
as a private field this will overloads parent class value. So this private
field must be removed.
[CLEANUP] - fix junit test avoid using obsolete asserts
PDI-12140 - junit tests provided

junit for different steps combination (regular step, step running in
multiple copies, partitioned steps)
PDI-12140 - IndexOutOfBoundsException when transitioning between different partition schemas

Fix transformation and BaseStep prepare execution logic.
For partitioning we had a case called 'Swim-lanes'. This is a case when we
have 2 steps partitioned with same partitioning schema. For swim-lines we
used to have N_to_N relationship. This is a special mapping when we used
to avoid extra buffers.
The issue was that when we use 2 steps with same patritioning count - but
different partitioning we used to treat this case as a swim lines by
mistake.
This was lead to IOB exception. This case could be workarounded using one
not partitioned step between.
But since we allow to put 2 differenly patritioned steps in line - we
should correctly handle this case. Even it is not optimal transformation
order lead to excessive rowsets.

This commit brings refactoring for steps rowsets relation discovery and
should fix IOOB exception.
[PDI-12521] - Google Analytics Data Input Step missing collections library - replace conflicting dependency
[PDI-11344] - Blocking step poor performance because of not setting BaseStep.first to false - revert test as it should be placed in engine module
[PDI-11344] - Blocking step poor performance because of not setting BaseStep.first to false - introduce test
Merge pull request #714 from akhayrutdinov/PDI-11344

[Pdi 11344] - Fix test's failing