lisk-sdk: Inconsistency in migrations

Expected behavior

N/A

Actual behavior

There are several inconsistency in our migration process:

• Files 20161016133824_addBroadhashColumnToPeers.sql 20161016133824_addHeightColumnToPeers.sql have same ID, that can result with second migration beign not applied correctly on some nodes. We should change ID of second migration and try to re-execute it if needed (change query to ALTER TABLE "peers" ADD COLUMN IF NOT EXISTS "height" INT;)
• Query that inserts to migations table have ON CONFLICT DO NOTHING, which is not acceptable, as migration should be only executed (and then inserted) once.
• After renaming all SQL files to underscore case (in https://github.com/LiskHQ/lisk/pull/1455) - entries in migrations table still contains old migration names for already executed migrations. For consistency entries in database should match new names.
• We should review migration script if it sorts migrations based on ID ascending and then executes them, because migrations should be executed in strict order.

Steps to reproduce

N/A

Which version(s) does this affect? (Environment, OS, etc…)

1.0.0