Don't "Follow" when dumping test pod logs.

[mattmoor]

"Follow" is for watching for additional logs and printing them as they appear (e.g. tail -f), it only stops when the Pod itself goes away. This is inappropriate for the type of post-mortem log dumping we are doing here.

I've seen a number of timeout_test.go stack traces still after my context.WithTimeout changes, which trace back to this line. Things are deadlocked on this line until the test times out.

/kind bug

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Includes tests (if functionality changed/added)
• Includes docs (if user facing)
• Commit messages follow commit message best practices
• Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.

Double check this list of stuff that's easy to miss:

• If you are adding a new binary/image to the cmd dir, please update
  the release Task to build and release this image.

Reviewer Notes

If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

Release Notes

NONE

[mattmoor]

/assign @vdemeester @afrittoli @imjasonh

[imjasonh]

/lgtm

[afrittoli]

Sounds good.

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: afrittoli

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 [afrittoli]

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