Search order for locations in HFileLink

Found that search order for locations is following the order of these locations added to HFileLink object. 

setLocations(originPath, tempPath, mobPath, archivePath);

archivePath is the last one to be searched. For most cases, hfile exists in archivePath, so we can move archivePath to the first parameter to avoid unnecessary NN query.