The purpose of the PR is to store who made the latest changes to workbench resources. This is done by storing the username of the user to all the resources tables, except notebook

• The reason why lastModifiedBy is using just username is to have consistency. Since workbench doesn't store notebook information and it can be locked or updated by external users as well. Hence we just use the username for all resources.
• We could use a user ID for history tracking, which would allow us to enforce data integrity in the database. However, we want this information to persist in the event of deleting a user and our current user deletion process removes them from the database rather than marking the record as deleted.

Description:

PR checklist

• This PR meets the Acceptance Criteria in the JIRA story
• The JIRA story has been moved to Dev Review
• This PR includes appropriate unit tests
• I have added explanatory comments where the logic is not obvious
• I have run and tested this change locally, and my testing process is described here
• If this includes a new feature flag, I have created and linked new JIRA tickets to (a) turn on the feature flag and (b) remove it later
• If this includes an API change, I have run the E2E tests on this change against my local server with yarn test-local because this PR won't be covered by the CircleCI tests
• If this includes a UI change, I have taken screen recordings or screenshots of the new behavior and notified the PO and UX designer in Slack
• If this change impacts deployment safety (e.g. removing/altering APIs which are in use) I have documented these in the description
• If this includes an API change, I have updated the appropriate Swagger definitions and updated the appropriate API consumers
  • AoU UI
  • Perf tests
  • Researcher Directory export
  • Cron tasks - for Offline*Controllers
  • SumoLogic - for EgressAlert