Describe the bug:
When testing the new index hasData service, I have found two 3 permission issues. Two refer to when a user has no read index privileges.

Scenario one:

1. There are 3 indices
2. User has read access to 1 of the indices, but not to the other two
3. The service will return false and we will show a no data screen, thus blocking access to Discover. The user should be able to see the index they have access to.

Scenario two:

1. There are 3 indices
2. User has no read permissions to any indices
3. The service will return false and will show a no data screen. This is not as severe as a the first part (as from the user's standpoint there really is no data they could see), but it would be nice if the service would throw some sort of an error that we could leverage then to display an appropriate message.

The third issue refers to a scenario where the user has read access to the index, but no view_index_metadata privileges. In that case the user has no permissions to view if they have permissions 🤯 I am not sure what the expected scenario here is but apparently this is a valid use-case. It feels like we shouldn't be blocking users from the access to the index they have access to.

Can we get the fix for this prioritized for 8.3.0? cc @shivindera