test: enable timeouts for running E2E commands

[jackfrancis]

Reason for Change:

Enable setting an upper bound time limit on E2E test commands. The specific use-case is ensuring that simple pod-to-pod networking operations are consistently quick and don't fall victim to, for example, occasional > 5 second DNS lookup operations.

Issue Fixed:

Requirements:

• uses conventional commit messages
• includes documentation
• adds unit tests
• tested upgrade from previous version

Notes:

[codecov]

Codecov Report

Merging #563 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #563   +/-   ##
=======================================
  Coverage   56.74%   56.74%           
=======================================
  Files          91       91           
  Lines       13870    13870           
=======================================
  Hits         7870     7870           
  Misses       5336     5336           
  Partials      664      664

[serbrech]

Can you make the timeout a const parameter where it makes sense?

[CecileRobertMichon]

what about all the hardcoded 60 second timeouts in cli.go?

[jackfrancis]

@CecileRobertMichon that's a different timeout enforcement which is ensuring "fail fast" when something goes wonky with pre-requisite az commands.

The purpose of this changeset is to enable timeouts for kubectl run-type commands; to be able to detect, for example, regular 5 second name lookups in the pod networking stack.

[CecileRobertMichon]

/lgtm

[acs-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CecileRobertMichon, jackfrancis

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [CecileRobertMichon,jackfrancis]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment