fix(server): Report v1.Status errors. Fixes #3608

[alexec]

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
• The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
• I've signed the CLA.
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My builds are green. Try syncing with master if they are not.
• My organization is added to USERS.md.

Fixes #3608

I was incorrect in my solution to #3608. Re-establishing a watch can result in an infinite loop and therefore the server consuming 100% CPU. One instance when this happens is when listOptions.resourceVersion has "too old resource version" (e.g. old browser window left open).

This PR does:

• Essentially reverts the original fix.
• Reports v1.Status errors as warnings rather than error in the workflow-logger.go.
• Return a v1.Status error back to the client for workflow watch.

[alexec]

Fixed and available in v2.10.0-rc5.