feat(server): Backfill missing_fields on _nango_config

[nalanj]

Fills out missing_fields as best as we can based on _nango_config. Unfortunately the CUSTOM auth_method won't be able to be backfilled performantly, but all others were possible.

For all of these, the prior PR will cause them to show errors in the future when created or edited, so I think we're safe here without having to decrypt all of the CUSTOM auth based ones.

https://linear.app/nango/issue/NAN-2168/surface-integrationsconnections-errors-in-nango-ui

How I tested

• Run the migration against dev db with oauth and app auth_method integrations that don't have their settings filled and don't have errors set yet. Feel free to just clear missing_fields in the DB as an easy way to handle that.
• Confirm in the database that the fields were correctly filled after the migration runs.

[linear]

NAN-2168 Surface integrations/connections errors in Nango UI

[nalanj]

In Slack we discussed adding auth_mode to _nango_configs, and it's more complicated than is desirable right now, with not much downside in terms of future work to write a migration and do it later, so we'll handle that in the future if needed.

[TBonnin]

Can we estimate how fast the migration gonna be in prod? How many integrations do we have to go through?

[bodinsamuel]

You can make the script faster by skipping deleted one (about 25% in prod)

[nalanj]

@TBonnin There are only 16240 in prod, so this should run pretty quick, especially since I was able to remove any need to decrypt fields.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
8205899	Triggered	Generic Password	dde28f4	packages/database/lib/getDbConfig.ts	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}