[MINT-2720] Data Exchange Approach

[OddTomBrooks]

MINT-2720

Description

Created Data Exchange Approach in accordance with Figma spec.

• Backend
  • GQL
  • SQL
  • Store Methods
  • Postman
  • Resolvers

How to test this change

1. Bring up containers
2. Create a model plan with postman
3. Validate that the model plan has a Data Exchange Approach task list section
4. Update corresponding Data Exchange Approach task list section with postman

PR Author Checklist

• I have provided a detailed description of the changes in this PR.
• I have provided clear instructions on how to test the changes in this PR.
• I have updated tests or written new tests as appropriate in this PR.
• Updated the Postman Collection if necessary.

PR Reviewer Guidelines

• It's best to pull the branch locally and test it, rather than just looking at the code online!
• When approving a PR, provide a reason why you're approving it
  • e.g. "Approving because I tested it locally and all functionality works as expected"
  • e.g. "Approving because the change is simple and matches the Figma design"
• Don't be afraid to leave comments or ask questions, especially if you don't understand why something was done! (This is often a great time to suggest code comments or documentation updates)
• Check that all code is adequately covered by tests - if it isn't feel free to suggest the addition of tests.

[StevenWadeOddball]

Thanks Tom, this is just a high level review of the data type in graphql. There is some deviation from FIGMA that I wanted to call out now instead of waiting till the PR is promoted.

[patrickseguraoddball]

I'm getting this error when creating a model plan and trying to query status

{
  "errors": [
    {
      "message": "the requested element is null which the schema does not allow",
      "path": [
        "modelPlan",
        "dataExchangeApproach",
        "status"
      ]
    }
  ],
  "data": null
}

[ClayBenson94]

I'm getting this error when creating a model plan and trying to query status

{
  "errors": [
    {
      "message": "the requested element is null which the schema does not allow",
      "path": [
        "modelPlan",
        "dataExchangeApproach",
        "status"
      ]
    }
  ],
  "data": null
}

@OddTomBrooks can you add a NOT NULL and DEFAULT value in the migration to avoid this?

EDIT: Wait, that's already there. Not sure why this'd come back null in GQL 🤔

EDIT 2: Looks like we might need to add status to the return values of the SQL scripts that do CRUD operations for the data exchange table

[StevenWadeOddball]

Thanks Tom, I think this is in a good state to merge to a feature branch. There are some thing that I think can be updated, but I think it would be better to merge this, and iterate on another PR.

I'd like to revisit the core struct before this targets main. I left a comment for a few other things I noticed, but as I don't think they will affect the front end, I think they can be addressed later.

[StevenWadeOddball]

A note in case this file gets touched again, we have sqlutils.Get and Select procedures to handle most of the boilerplate for database calls. It can replace much of the existing code to prepare named statements here.

changes made