Update the last TCR when creating a TCER

When large enterprise ETM deployments have projected data scale growth exceeding the maximum capacity of ETM, one solution is to reduce the number of test artifacts created in ETM.  As TCRs are one of the most abundant test artifact types, customers need a mechanism go decrease the number of new TCRs without manually deleting existing TCRs (see https://jazz.net/wiki/bin/view/Main/StrategiesAndToolsToReduceTheETMDatabaseSize).  For some customers, when running a TCER multiple times, the intermediate TCRs (all TCRs except the last TCR) are not required.  As such, customers need support for running TCERs and updating (e.g. replacing all previous execution properties/sections with the new execution properties/sections) the last TCR instead of creating a new TCR.  

This enhancement requires the following:

1. Enabling/disabling (default: disabled) this support in Manage Properties, including support for copying the Project Property using the ETM Copy Project Properties Utility.

2. Support for manual, offline, automated, and multiple TCER(s) execution and creating a TCR without execution.  Note, automated test execution support may require updates to the ETM Execution Tool, ETM Adapter Library, and/or existing test execution adapters.

Notes:

1. TSER execution is not required currently since test suites are currently not used but recommended for consistency and to support the future use of test suites.

2. TCR history provides a mechanism to view the past executions of the TCER.