e2e: Easier to follow log

[nirs]

Additional log cleanups split from #1628:

• remove the file:line since it make it harder to follow the log and does not add much value.
  • it could be nice to have it we could move it to the end of the log How to add file:line info at the end of the log message? uber-go/zap#1471
  • I checked zap code, the location of the caller is hard-coded. The only way is to use our own encoder that will convert file/line info to field, which logged at the end.
  • We can remove the caller in the console logs when we have a log file (e2e: Add logfile #1722)
• Remove unhelpful noise from test name "Deploy", "busybox"
  • deploy will be useful when we add other workloads (statefulset, daemonset, vm)
  • busybox can be removed - the name will be in the specific workload debug logs

[nirs]

Summary from discussion with @raghavendra-talur:

We want to replace the current format:

{deployer}-Deploy-{rbd|cephfs}-busybox

With:

{deploy|statefulset|daemonset|vm}-{block|file}-{deployer}-{volrep|volsync}

(I'm not sure about the order)

So the tests are about:

• The workload
• The volume mode (different modes need different deployment script for busybox)
• The way the workload is deployed
• The way we protect the workload

And not about specific storage provider (rbd, cephfs) - Ramen is storage agnostic.

The config determines the particular storage to use for the test. The same test will work on drenv, openshift, k8s, with any compatible storage,