Merge RTK APIs

[allisonking]

Closes #1386

Code Changes

• Merges all of our createApis into one!
  • ...almost. the exception is the healthApi since that one isn't prefixed by /api/v1. we could write a wrapper around our baseApi if we really wanted them all to use the same one, but the healthApi is a bit of an outlier for not being under /api/v1 imo, so I left it as-is for now
• Fix some backend endpoints to use the APIRouter that handles trailing slashes
  • This became apparent because many of the traditional "ops" query calls were not using nextjs rewrites, and instead were swapping out the query call to localhost:8080. this is not ideal, since then you can run into cors problems when developing locally (I think our backend might allow cors to work around this though, I haven't looked into this recently). Once I updated those endpoints to use nextjs rewrites, the trailing slash problem cropped up since next always adds a trailing slash
• Consolidate data category API calls. The datamap UI had a separate API for this, now it uses the same one
• Refactor store.ts to be more consistent and make more sense (imo 😄 )
• Use consistent tag names (we had i.e. "CustomFieldDefinition" and "Data Category". I made them all space separated since RTK can handle it and I think it's more readable that way)

Steps to Confirm

• Everything still works 🤞 Would be good to run the QA tests here since this touches nearly all of the API calls the FE makes

Pre-Merge Checklist

• All CI Pipelines Succeeded
• Documentation:
  • documentation complete, PR opened in fidesdocs
  • documentation issue created in fidesdocs
• Issue Requirements are Met
• Relevant Follow-Up Issues Created
• Update CHANGELOG.md
• For API changes, the Postman collection has been updated

Description Of Changes

Write some things here about the changes and any potential caveats

[cypress]

Passing run #1727 ↗︎

0

4

0

0

0

Details:

Merge 79b0fb6 into 1aa3219...
Project: fides	Commit: 033e1aaaac ℹ️
Status: Passed	Duration: 00:45 💡
Started: May 3, 2023 12:50 PM	Ended: May 3, 2023 12:50 PM

_{This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.}

[codecov]

Codecov Report

Patch coverage: 100.00% and project coverage change: +0.02 🎉

Comparison is base (1aa3219) 87.37% compared to head (267188b) 87.39%.

❗ Current head 267188b differs from pull request most recent head 79b0fb6. Consider uploading reports for the commit 79b0fb6 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3059      +/-   ##
==========================================
+ Coverage   87.37%   87.39%   +0.02%     
==========================================
  Files         313      313              
  Lines       18241    18242       +1     
  Branches     2366     2365       -1     
==========================================
+ Hits        15938    15943       +5     
+ Misses       1871     1867       -4     
  Partials      432      432              

Impacted Files	Coverage Δ
.../ops/api/v1/endpoints/connection_type_endpoints.py	100.00% <100.00%> (ø)
src/fides/lib/oauth/api/routes/user_endpoints.py	95.45% <100.00%> (+0.05%)	⬆️

... and 2 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[TheAndrewJackson]

@allisonking This is awesome! It's great to have everything be unified together.

I'm running into some issues with logging in. I'm using nox -s "dev(slim)" in plus. When I try to login I get a 405.

Did you experience this at all while developing?

[allisonking]

@allisonking This is awesome! It's great to have everything be unified together.

I'm running into some issues with logging in. I'm using nox -s "dev(slim)" in plus. When I try to login I get a 405.

Did you experience this at all while developing?

Ah yeah auth was one of the endpoints that needed the trailing slash fix, which is only in this branch. So when you do a nox -s "dev(slim)" in plus, it doesn't get that fix yet (at least that's my theory!)

See if things work for you using nox -s dev in fides first, then maybe we can use some of Adam's fancy new release branch tagging to test things out with plus! (I think we'd have to create new tags, and I don't know if that would interfere with the ongoing release right now)

[TheAndrewJackson]

@allisonking The changes not being propagated to fidesplus was the issue. Everything is working great!