feat: add support for streaming container logs from services

[smlx]

Checklist

• Affected Issues have been mentioned in the Closing issues section
• Documentation has been written/updated.
• Changelog entry has been written

This PR adds support for this new log access feature in ssh-portal: uselagoon/lagoon-ssh-portal#243
It allows you to access container logs from any Lagoon environment that you have permission to SSH to, via the command line.

The command can either collect existing logs, or "follow" live logs via -f.

Please do not merge this until uselagoon/lagoon-ssh-portal#243 is merged, and lagoon-charts is updated to a version with this feature.

Changelog Entry

Feature - access logs from the CLI (#232)

Closing issues

Closes: #232

[seanhamlin]

This would be amazing, several customers have mentioned that having to wait for ElasticSearch to have logs can be 30-60 seconds delay, and the logs can be out of order. Having more real time logs, in the correct order would be ace.

[shreddedbacon]

It is coming, just need support for the feature in the charts.

[shreddedbacon]

The only thing I wanted to verify before merging this was the error someone would get if the ssh-portal does not have support for logs enabled yet. And the failure message isn't that great.

Error: couldn't dial SSH: ssh: handshake failed: knownhosts: key mismatch
exit status 254

I'm not sure if there is a better way to determine if the logs endpoint is just disabled or not though from the error, as this gives the impression that the SSH service has an issue, but using ssh works.

[shreddedbacon]

I can update the default return message for the dial error that mentions that it is possible that the logs endpoint is just disabled though, but it would show for all dial errors