Migration run with specific name does not check if migration was already executed in status.json

[IvanKiral]

Brief bug description

What went wrong?
Running the already executed migration is aborted by error from the management client.

Repro steps

1. Run some migration with for example in range (migration run --range 3:5)
2. Run migration run -n "alreadyExecutedMigration" and it gives the error from the ManagementClient.

Expected behavior

Should skip the already executed migration.

Test environment

• Platform/OS: [e.g. .NET Core 2.1, iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Additional context

Add any other context about the problem here.

Screenshots

Add links to screenshots, if possible.