event resolver errors through to upbound-graphql when unable to get involvedobject

[jastang]

Hit this issue (slack thread) because the involvedobject (some pod) no longer existed, which would throw in xgql:

xgql/internal/graph/resolvers/event.go

Line 161 in 0a1d4ae

graphql.AddError(ctx, errors.Wrap(err, errGetInvolved))

could we be more resilient?

[thephred]

We are not investing further in xgql unless pressed hard.