Changes

Disabled URLRetrieveTestCancelConnectJob since irrelevant for 45
provider
Change-Id: I524f2fb1dae21c02b7192f2820c4a442199b790e

Bug 544447 - [provider] Implement filetransfer provider using HttpClient
4.5 API
Keep HttpResponse after closing the transfer, since it might still be 
accessed afterwards.
Change-Id: I31321dd1ba416d097a4619949e446214be859ecf Signed-off-by:
Carsten Reckord <reckord@yatta.de>

Bug 544447 - [provider] Implement filetransfer provider using HttpClient
4.5 API
Make sure connection is closed in hardClose().
There are four cases to consider:
1. Transfer is complete 2. Transfer was cancelled 3. There was an
exception during transfer 4. The transfer was paused
In case 3, hardClose() is called from cancel() directly, in the other 
cases it gets called from the finally block in performFileTransfer().
Cases 1-3 are easy: In case 1, the stream encountered EOF, isDone() == 
true, and the connection was already closed as a result. In case 2 and
3, it is obvious that we want the connection closed as a result.
In case 4, we might want to resume later, but when resuming, we are 
actually creating a new HttpGet request and get a new HttpResponse as a 
result. So we also want to close the previous one when pausing.
Change-Id: I3daf3c34d0784e5c19aa38441ba373422796f538 Signed-off-by:
Carsten Reckord <reckord@yatta.de>

Bug 544447 - [provider] Implement filetransfer provider using HttpClient
4.5 API
Introduced property to control shared HttpClient instance vs new one for 
every transfer.
Change-Id: I734c921a6a35ea201ad904121143c7284c5bb648 Signed-off-by:
Carsten Reckord <reckord@yatta.de>

Bug 544447 - [provider] Implement filetransfer provider using HttpClient
4.5 API
Use shared HttpClient by default
Change-Id: I5252cace3db328dddb541e5c7e9bea8597722486 Signed-off-by:
Carsten Reckord <reckord@yatta.de>

Customise the name of the repository zip file.
(Avoids the manual step of renaming the zip)
Change-Id: I0f16fd63ef2d94c41e17d20f82161dc98a8577a8 Signed-off-by: Mat
Booth <mat.booth@redhat.com>

Fix errors in 2019-03 target platform
The 2019-03 target platform definition file was still pulling in some
Photon bundles instead of the 2019-03 versions. This change fixes this,
so we can be more confident that ECF contiues to build on all supported
versions of the Platform
Change-Id: Ic24266fe0f84292fe2d1526645e29dc69cf395ae Signed-off-by: Mat
Booth <mat.booth@redhat.com>