Issue 368: Prompt the user *again* if a pending migration is detected. Optionally disable.

[kmanning]

• Issue FlywayPlugin: Prompt the user *again* before applying migration #368
• Applying a migration may be an uncommon case - more commonly, no pending migration may exist
• Because this is an uncommon occurrence, a user may not be accustomed to validating during the "plan" stage whether or not a pending migration exists.
• As an extra safe guard, optionally prompt the user again if a migration is detected - reconfirm that the user is aware that a pending migration exists, and approves the application of said migration.
• This should be optional

[kmanning]

Suggested implementation:

• Tee the flyway output (and handle failure cases properly)
• Grep the output for Pending (The various statuses are available here - https://flywaydb.org/documentation/concepts/migrations#migration-states)
• If a Pending status is detected, prompt the user, "A pending migration was found - please review your flyway output. Do you want to continue and apply the migration?"

[codecov-commenter]

Codecov Report

Merging #371 (e42fe51) into master (7c4dbaf) will increase coverage by 0.27%.
The diff coverage is 95.23%.

@@            Coverage Diff             @@
##           master     #371      +/-   ##
==========================================
+ Coverage   80.53%   80.81%   +0.27%     
==========================================
  Files          51       51              
  Lines        1408     1428      +20     
  Branches      311      314       +3     
==========================================
+ Hits         1134     1154      +20     
  Misses        122      122              
  Partials      152      152              

Impacted Files	Coverage Δ
src/FlywayMigrationPlugin.groovy	96.07% <95.23%> (+2.53%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7c4dbaf...e42fe51. Read the comment docs.