Have crossplane beta render emit debug logs

[negz]

What problem are you facing?

Today crossplane beta render doesn't log much (anything?). There's a bunch of TODOs in the codebase where it would be useful to do so - e.g. if we can't stop a Function running as a Docker container.

How could Crossplane help solve your problem?

We should add some debug logging statements. Given that the command's main job is to print stuff to stdout we probably need to be careful about logging. I imagine we don't want to log anything in the happy path, and if we do hit issues we want to make sure they're going to stderr so the caller can filter output from logs.

[github-actions]

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

[jbw976]

/fresh

[phisco]

Logging to stderr should be enough to avoid confusion with the actual output, wdyt @negz?