feat: script runner data transfer part 1

[YazeedLoonat]

Issue Overview

This PR addresses #issue

• This change addresses the issue in full

Description

This creates an endpoint in the script runner controller, and a function in the script runner service to start doing data transfer

The new endpoint takes in the database connection string in order to connect to the db

How Can This Be Tested/Reviewed?

Spin up the api locally -> head to lhttp://localhost:3101/api/ or http://localhost:3100/api/ -> get the production database connection string -> log in as an admin or juris admin user via the openapi doc -> hit the script runner's data transfer endpoint passing in the database connection string

you should get success: true on the openapi response, and your api terminal should have a console log with the jurisdiction id for San Mateo from the production db

Checklist:

• My code follows the style guidelines of this project
• I have added QA notes to the issue with applicable URLs
• I have performed a self-review of my own code
• I have reviewed the changes in a desktop view
• I have reviewed the changes in a mobile view
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have assigned reviewers
• I have run yarn generate:client and/or created a migration if I made backend changes that require them
• My commit message(s) is/are polished, and any breaking changes are indicated in the message and are well-described
• Commits made across packages purposefully have the same commit message/version change, else are separated into different commits

Reviewer Notes:

Steps to review a PR:

• Read and understand the issue, and ensure the author has added QA notes
• Review the code itself from a style point of view
• Pull the changes down locally and test that the acceptance criteria is met
• Also review the acceptance criteria on the Netlify deploy preview (noting that these do not yet include any backend changes made in the PR)
• Either explicitly ask a clarifying question, request changes, or approve the PR if there are small remaining changes but the PR is otherwise good to go

On Merge:

If you have one commit and message, squash. If you need each message to be applied, rebase and merge.

[netlify]

✅ Deploy Preview for bloom-exygy-dev ready!

Name	Link
🔨 Latest commit	0bf352c
🔍 Latest deploy log	https://app.netlify.com/sites/bloom-exygy-dev/deploys/665608568d4037000845ca89
😎 Deploy Preview	https://deploy-preview-4104--bloom-exygy-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[mcgarrye]

LGTM