Looks like whenever we are running `cross-account-requests` API on non org-admin accounts the response is 403 and notifies a sentry of this error. Because we have limited amount of sentry backlock we should fire this request just if user is org admin or has rights to use cross acc request.

More details from gkaratae on slack:
hi, I have just debugged one of the most popular 403 errors from sentry: https://sentry.io/organizations/red-hat-it/issues/3568835302/events/6caef7f6b13e44ce98f9359c08a272a3/?project=1484024. don't remember if anyone else has already dug into it, but it turned out to be that insights-chrome is requesting this endpoint (even the query parameters totally match) most probably here. this is somewhat called notifier function which is though wrapped with try-catch, but once there is an error it console.errors it. The thing is, for non-administrators, basic users, this will always result in 403 from API. I think we better stop propagating the error to console unless there is an explicit reason for it