PCA Resyncing Logic (#668)

- Adding transaction.atomic() wrapper to webhook database calls, to reduce potential consistency errors between our StatusUpdate models and our Section model. This required modifying one of our existing test cases.
- Modifying logic for loadstatus management command to conditionally add StatusUpdate objects to ensure consistency between the last StatusUpdate and the status attribute of the Section model. registrarimport also uses loadstatus's logic, but it currently does not add StatusUpdate objects – this can be changed easily by setting add_status_update=True.
- Add sync_path_status management command to sync our database with path statuses in the case that OpenData's status API is inaccurate (we've historically seen this for around 4% of courses).

Author: shiva-menta

backend/Pipfile

@@ -63,6 +63,8 @@ python-dateutil = "*"
 docutils = "*"
 ics = "*"
 drf-nested-routers = "*"
+asyncio = "*"
+aiohttp = "*"
 
 [requires]
 python_full_version = "3.11"

backend/Pipfile.lock

@@ -132,15 +132,16 @@ def accept_webhook(request):
         else:
             response = JsonResponse({"message": "webhook recieved"})
 
-        u = record_update(
-            section,
-            course_term,
-            prev_status,
-            course_status,
-            alert_for_course_called,
-            request.body,
-        )
-        update_course_from_record(u)
+        with transaction.atomic():
+            u = record_update(
+                section,
+                course_term,
+                prev_status,
+                course_status,
+                alert_for_course_called,
+                request.body,
+            )
+            update_course_from_record(u)
     except (ValidationError, ValueError) as e:
         logger.error(e, extra={"request": request})
         response = JsonResponse(