fix(ui): default to main container in Sensor logs. Fixes #9459

[jsvk]

Fixes #9459

[terrytangyuan]

What problem is this trying to solve?

[jsvk]

sorry still working on the write-up (in the form of Github Issue, hope that's ok), but the short summary is we're injecting a sidecar container via mutating admission controller to the Sensor pod (fluent-bit in our case, for forwarding logs to Splunk).

Without specifying the container, the UI fails to load the logs and instead returns with a 504 - Gateway Timeout.

Error logs in the Server pod say it encountered this error -

time="2022-08-25T14:30:21.960Z" level=error msg="a container name must be specified for pod adobe-platform--[snip], choose one of: [main fluent-bit]" namespace=ns-team-adobe-platform--[snip] podName=adobe-platform--[snip]

I saw the API does support parsing podLogOptions.container, and so by appending ?podLogOptions.container=main to the API call, I confirmed the call returns instantly with the logs we expect, so this is a matter of updating this at the UI level.

Is there a better approach I'm not thinking of?