Feat/ssn table

[jusdino]

Description List

• Added minor improvements to API/Lambda logging to make tracing requests easier
• Moved SSN/provider_id association records into a separate DynamoDB table
• Encrypted that table with a very restrictive key
• Added a resource policy to the table that prevents bulk data read/write
• Integrated required permissions across license ingest and API query workflows

Testing List

• bin/run_tests.sh
• Please manually ETE test by:
  • Deleting all provider data from your sandbox
  • Upload a mock data CSV via the UI, for two different states (requires a user with write permission in two states)
  • Wait ~5 minutes
  • Query for licenses
  • Query for a particular SSN
  • Verify that the provider record has two licenses associated (one for each state)
• Code review

Closes #
#396

[landonshumway-ia]

Question about the inverted GSI that we will likely want to document the answer to.

[jusdino]

@jlkravitz , this one is ready for you!

[jlkravitz]

• review the pull request to get oriented
  • read the description of the pull request, which should summarize the changes made
  • read through every task on the Scrum board that's encompassed by this pull request
  • read the description of the commits that comprise the pull request
• skim all new code, in the context of existing code, looking for problems (knowing that the vast majority of new code will be covered by tests)
• review all tests
  • methodically review all new tests for correctness, quality of naming
  • look at code coverage of tests
  • determine what code isn’t tested, review that rigorously
• review documentation to ensure that it matches changes
• provide comments on the pull request on GitHub, as necessary
  • for comments that are specific to a particular line of code, comment on those specific lines
  • for comments that are more general, attach the comment to a random line in README.md (as opposed to commenting on the pull request itself), to be able to use GitHub's ability to thread discussions on those comments

[jlkravitz]

Looks great! Thanks for being so detail-oriented on this one. Few questions/comments.

[jusdino]

@jlkravitz, alrighty, this one is back in your court.

[jlkravitz]

@isabeleliassen This is good to go.