feat: merge prisma backend

[ludtkemorgan]

Pull Prisma changes over to HBA

• This change addresses the issue in full
• This change addresses only certain aspects of the issue
• This change is a dependency for another issue
• This change has a dependency from another issue

Description

This pulls all of the changes from core into HBA. A majority of this is the Prisma changes, but there are a few changes that are in core and not yet here.

Because of the way the commits are in main from the prisma merge I was unable to cherry-pick. Instead I did a merge from core. This means that git thinks there are commits going back almost 2 years that are a part of this change. So ignore the commits, but rather the actual changes.

Note:

• There was well over 200 files that had merge conflicts and I did my best to look for anything that might be weird. There was a few places that differ from Core and I kept those how they were in HBA.

How Can This Be Tested/Reviewed?

Both the partner and public sites should work e2e using the new backend.

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.

[YazeedLoonat]

This looks fantastic!
Only thing I found was:
the user export seems to have a problem where it both doesn't download in the web browser and also doesn't actually send an email out

[ludtkemorgan]

@YazeedLoonat The email of the user export should be working. Are you logged in with an account to your email and not the admin account?

[emilyjablonski]

Do you know where this change is coming from?

[ludtkemorgan]

I'm trying to get the cypress tests to pass and this was a theory since I get a warning about "There is no step defined which matches preferences". That did not solve the issue of running the cypress tests in ci so I'll remove it. But it is a warning that we might want to address at some point.

For the cypress issue. It appears that for some reason only one of the two address verification steps is happening on circleCi when both of them happen when running locally. And they work correctly in Core. So still digging into it

[ludtkemorgan]

ok, I reverted this change and I got the cypress public test working. I don't know why it was working locally but it was an issue with additional data in the application data for the cypress test.

[ColinBuyck]

I recognize that this is happening in Core as well but I'm just noticing that export files are saved on the backend. Is that temp folder automatically deleted at some point? Are there any concerns with doing this with production-level usage?

[YazeedLoonat]

@ColinBuyck

I recognize that this is happening in Core as well but I'm just noticing that export files are saved on the backend. Is that temp folder automatically deleted at some point? Are there any concerns with doing this with production-level usage?

Hello! we have a cronjob that runs every so often that will clear that folder of all data

we were running into collisions with the testing which indicated that deleting the files immediately could cause issues on production which files being deleted before they were sent

[YazeedLoonat]

Hey @ludtkemorgan :sigh: I created a user for myself then forgot to use that user

whoever own [email protected] got a whole bunch of user exports lol

giving this the approval from me

[ColinBuyck]

LGTM 🕹️ Thanks for the clarification @YazeedLoonat!