Indices API: Fixed backward compatibility issue

If a 1.4 node needs to forward a GET index API call to a <1.4 master it cannot use the GET index API endpoints as the master has no knowledge of it. This change detects that the master does not understand the initial request and instead tries it again using the old APIs. If these calls also do not work, an error is returned

Closes #8364
My take on this was, we know why the first exception (e) occurs since we have confirmed that it was ActionNotFound, so we can be pretty sure we are talking to a node on a previous version. Given that, we don't want to hide a 'real' exception such as IndexMissingException so is better to return the new exception (e1). WDYT?