feat: add support for sequlize migration options

[tim-yao]

For suggestion from #652

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[tim-yao]

@googlebot I signed it!

[patrickhulce]

thanks very much for the contribution @tim-yao! :D

impl LGTM, just a test request

[patrickhulce]

could you put this line in a finally block? if our query fails we still want the server connection to close so test process will exit :)

[tim-yao]

Thanks @patrickhulce! Updated.

[patrickhulce]

also fyi have some lint errors to fix :) https://github.com/GoogleChrome/lighthouse-ci/pull/653/checks?check_run_id=3094377453#step:9:33

[patrickhulce]

@tim-yao I think we're running into issues with the test being run in the same set as the original mysql test because they're using the same DB. let's just go ahead and change the existing test to use the custom migration table name and add our assertion there rather than re-run the mysql set. WDYT?

[patrickhulce]

That or switch to sqlite database in a new file name that's a separate DB.

[tim-yao]

@tim-yao I think we're running into issues with the test being run in the same set as the original mysql test because they're using the same DB. let's just go ahead and change the existing test to use the custom migration table name and add our assertion there rather than re-run the mysql set. WDYT?

That make sense to me. Will do it.

@patrickhulce any idea? I get these errors in test with the new migration configs.I can see them in the CI as well.

[patrickhulce]

any idea? I get these errors in test with the new migration configs.I can see them in the CI as well.

You haven't pushed the latest version with the suggestion so I'm not sure. Those errors are expected with the version of the code that has been pushed here (the databases are being reused between 2 tests with unexpected state).