Prefer index name when mapping unique constraint errors

When using migrations to create indexes instead of sync or when unique
index name has fields with underscores (was problem at least with
postgres implementation) then it was not possible to set custom error
message, because mapping the error thrown from database always failed.
Fixed by using indexName always for mapping the error if possible.
Update changelog
Promisify tests
Do not explicitly call done in the tests of customized error message of
unique constraint error
Merge pull request #2568 from jamonkko/master

Prefer index name when mapping unique constraint errors
Fix MySQL unique constraint error message parsing
Update inflection dependency to v1.5.2
Merge pull request #2575 from overlookmotel/Fix-unique-constraint-parsing-bug

Fix MySQL unique constraint error message parsing
Merge pull request #2578 from overlookmotel/inflection-v1.5.2

Update inflection dependency to v1.5.2
remove faulty logic in update code
Conflict Merge
accidentally an only
Merge pull request #9 from mbroadst/fix-update-logic

remove faulty logic in update code
unify selectQuery between abstract and mssql dialects