ENSCORESW-929: added some sanity checks for the location string
saves us from huge stack traces if location was wrong
ENSCORESW-929: for endpoints using regions, add a sanity check to make sure the location string is sensible
bail out early before any API calls if it is not, to avoid lengthy stack traces
remove try/catch block from internal method, only needed once in the GET/POST methods
end is allowed to be negative
better regular expression to catch location strings in correct format, but with wrong start/end
better try/catch block to deal with stack traces from Ensembl and custom errors
catch errors that could be coming from API stack trace
additional check on coord_system_name
no catch block for POST, or we die for one failed out of 100
added check to see if stable id was found, raise exception if not
if end undefined, set it to start
more sanity checks for vep urls
regexp expanded to check for strand as well
regexp corrected to cover more cases
improved regexp
moved feature fetch method from controller to model
for POST, try block foreach id, otherwise we exit early if a single entry fails
regexp modified again