Enhance logging for CI

When CI pipeline fails, it dumps out a lot of information about helm releases, pods, etc. But, it is still not enough information to identify exactly what went wrong.

Add additional logging to help identify exactly what went wrong. Some ideas include:

• Identify which resource(s) did not deploy so user does not have to search through the logs
• From the resource(s) that failed, dump events using get events to identify the errors
• Dump the logs x lines of the log (both current and previous) for failed resources
• Dump denied opa gatekeeper violations (may need to enable log denies in gatekeeper)
• Dump denied network policy violations (if possible)
• Output other types of resources