Change the way index deletion works (part of #2811)
Change the way index deletion works (part of #2811)

* Instead of trying to figure out if an index is used by an FK ahead of time Sequel Pro will now simply run the query and check for the error code (and only for error 1553 will it attempt to also remove the FK)
* This means that a user will receive two remove dialogs in this rare case, but I think that is actually preferable. Common wisdom shows that users never read the first warning dialog, so in the past they may have agreed to something that they didn’t intend to do. The second dialog should actually make them pause and read it. Also there is a different confirmation button now.
* This also fixes the code to detect which FK in particular MySQL is referring to. SP should now correctly handle compound indexes and multi-column FKs as well as ambiguous results.

Jellyfrog/sequelpro,Jellyfrog/sequelpro,abhibeckert/sequelpro,Jellyfrog/sequelpro,abhibeckert/sequelpro,Jellyfrog/sequelpro,abhibeckert/sequelpro,abhibeckert/sequelpro