Improvements to bug reporting experience

[tranhl]

I'm seeing a couple of pain points come up for both users and maintainers when creating & triaging bug reports:

• No clear process/guidance on how to best report a bug
• It's unclear where diagnostics can be obtained
• Diagnostics may contain sensitive user/company data

Actions we can take to address these problems:

• Refactor action inputs logging into a single diagnostic report
• Implement log anonymization
• Introduce issue template
• Link to issue submission form above error logs to encourage error reporting
• Print diagnostics directly above error logs for convenience

[tranhl]

In terms of anonymization, the primary concern is sensitive information in branch names being exposed. Fundamentally, we only need insight into the node/leaf structure of the branch graph to do debugging. A potential approach to anonymization could be to replace feature/perennial branch names with unique human-readable stubs (e.g. feat/sensitive-company-work -> grain-loss-require-rocky).