Allow users to differentiate between different types of plugin failures

[ehmicky]

The current implementation of the plugin statuses does not allow users to know if a build failed due to a user error (e.g. wrong input), a plugin bug/crash, or a bug/crash from our code.
This is very valuable information for users trying to understand why their build failed.
It also would help redirect them to the right person: themselves, the plugin author or our support team.

Netlify Build has that information and can easily pass it on the API. We would need to add additional status state, e.g. failed_plugin (user error) vs bug_plugin (plugin bug) vs bug_core (bug from our code).

We would also need to surface this difference in the UI. What do you think?

[ehmicky]

This is becoming a bigger problem with Edge handlers. See #1895

[github-actions]

This issue has been automatically marked as stale because it has not had activity in 1 year. It will be closed in 14 days if no further activity occurs. Thanks!

[github-actions]

This issue was closed because it had no activity for over 1 year.