refactor: improve error handling on client side for change events

Description

This PR fixes an issue that was causing an error message to show on-screen for user accounts that don't have AIOPs or Event Intelligence capabilities.

With this changes instead of getting a non-inclusive error message users will see this image and message instead.

Issue number: #63

Type of change

[ ] New feature (non-breaking change which adds functionality)
[x] Fix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[x] I have performed a self-review of this change
[x] Changes have been tested
[x] Changes are documented
[x] Changes generate no new warnings
[x] PR title follows conventional commit semantics

If this is a breaking change 👇

[ ] I have documented the migration process
[ ] I have implemented necessary warnings (if it can live side by side)

Acknowledgement

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

PagerDuty / backstage-plugin