Also print random Redis element to debug that some FeatureRow has been ingested properly

Some tests (like ingestion test) expect the operation to complete in certain amount of time. This can only be guaranteed if the process have adequate CPU and memory.
Without it, when the test cluster is overloaded, the test process may get little CPU time allocated and the expected completion time is no longer valid

So we can obtain information about no of elements have been written in the pipeline without resorting to external metrics collector
This method makes use built in metrics util in Apache Beam

…he ingestion result in ImportJobTest