inefficient/non-performant crs-conversions causing reliability/performance issues on ingestion workflow

We are seeing reliability and performance issue because of inefficient/non-performant crs-conversions on ingestion workflow. If crs conversions takes long time (on Storage /batch API), then it slows down entire ingestion workflow.

There is a need for setting a timeout for crs-conversion requests that run for more than a certain time. For the requests to crs-conversion-service currently java.net.HttpURLConnection class is used, which is only has connectionTimeout and readTimeout properties, that don't help us to set the timeout.

It is suggested to use apache CloseableHttpClient httpClient that has socketTimeout property.

core-common MR - !213 (merged) storage MR - osdu/platform/system/storage!712 (merged)