Gather all operator logs on e2e test failure

[gflarity]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

This PR changes the e2e test diagnostic utility to gather all operator logs after a test failure, instead of just the last 2000 lines. This ensures complete diagnostic information is available when debugging test failures, rather than potentially missing earlier relevant logs that occurred before the failure.

Which issue(s) this PR fixes:

NONE

Special notes for your reviewer:

Small change to operator/e2e/tests/debug_utils.go:

• Removed the operatorLogLines constant (previously set to 2000)
• Removed the TailLines option from the pod log request, which causes it to fetch all logs

Does this PR introduce a API change?

NONE

Additional documentation e.g., enhancement proposals, usage docs, etc.:

NONE

[shayasoolin]

Might be safer to keep the tail, just have it much longer, say 32K lines.

[Ronkahn21]

Can we implement a line-limit control for logs? I recommend a parameter that defaults to -1 (unlimited). This is necessary because large test outputs (2,000+ lines) are currently flooding the terminal and cutting off vital early-stage debug data. Providing a way to redirect this to a file would also be a great solution.

[gflarity]

Can we implement a line-limit control for logs? I recommend a parameter that defaults to -1 (unlimited). This is necessary because large test outputs (2,000+ lines) are currently flooding the terminal and cutting off vital early-stage debug data. Providing a way to redirect this to a file would also be a great solution.

Ah, yes I can see how this is annoying. I'll add make it configurable, stdout vs write to file with a timestamp. Still stdout for github CI unfortunately.