If user tries to refresh a deleted index pattern in management, Kibana should warn the user instead of throwing 404 in console.

[bhavyarm]

Kibana version: 5.1.1 & master

Elasticsearch version: 5.1.1 & master

Server OS version: darwin-x86_64

Browser version: chrome 55.0.2883.95

Browser OS version: OS X

Original install method (e.g. download page, yum, from source, etc.): release build for 5.1.1 and qa build for master

Description of the problem including expected versus actual behavior: If an index pattern is deleted at the command line and user tries to click "refresh" on it in management in Kibana, Kibana throws 404 error in console instead of warning the user like it does in "Add new" index patterns.
In "Add new" screen Kibana displays "Unable to fetch mapping. Do you have indices matching the pattern?" when user tries to create an index pattern with a non-existent one. Perhaps the same message should get displayed for the former scenario too? or may be the deleted index pattern should be removed from getting displayed in management in Kibana?

Steps to reproduce:

1. Create an index pattern and configure it in kibana
2. Delete the index pattern in command line
3. Go to management and click refresh on the deleted index pattern
4. Kibana just throws 404 error in console

Errors in browser console (if relevant):
GET http://localhost:5601/elasticsearch/shakes*/_mapping/field/*?_=1482519565688&ignore_unavailable=false&allow_no_indices=false&include_defaults=true 404 (Not Found)

[w33ble]

Seems like there's some larger underlying problem with the way index patterns are used and checked. See also #9028 and #9224.

[w33ble]

This was actually closed as part of #10788