title: Flyway does not ignore out of order migration scripts, with outOfOrder=false
body: <p>I am not using outOfOrder.
  I would like to be able to add a migration script, that would not be the latest, (e.g. to bugfix an existing script, without changing that script).</p>
  
  <p>I would like the new script to be run, as part of the normal ordering, on databases that haven't been migrated yet.
  Any databases that are up to date (e.g. manually repaired) should ignore the new script.</p>
  
  <p>From the documentation:</p>
  
  <blockquote>
    <p>OutOfOrder - Allows migrations to be run "out of order". If you
    already have versions 1 and 3 applied, and now a version 2 is found,
    it will be applied too instead of being ignored.</p>
  </blockquote>
  
  <p>This suggests that the new script will be ignored, but I get the error:</p>
  
  <blockquote>
    <p>ERROR: Validate failed: Detected resolved migration not applied to database</p>
  </blockquote>
  
  <p>Will the new script only be ignored if the db baseline is ahead of it?
  Is this the expected behaviour?</p>
  
  <p>If so, I guess my solution here is either to:</p>
  
  <ul>
  <li>Use outOfOrder, and complicate all my scripts to be idempotent.</li>
  <li>Baseline my db after every migration.</li>
  </ul>