feat(accessLogsExport): create new endpoints TASK-1147

[RuthShryock]

👷 Description for instance maintainers

Create two new endpoints for access log exports which will return the status of the export job. One endpoint is restricted for superusers and allows them to access all logs while the other endpoint is for regular users to access their own logs.

👀 Preview steps

Test /api/v2/access-logs/export

1. Login to kpi as a super user.
2. Make a GET request to /api/v2/access-logs/export
3. If this is your first time accessing the endpoint, then verify you receive a 200 Ok with an empty list:

[]

1. If not, verify you receive a 200 Ok with a list of created export tasks:

[
    {
        "uid": "alezKqwR8diLDQEepA83Rz4V",
        "status": "complete",
        "date_created": "2024-12-03T17:29:21.602245Z"
    },
    {
        "uid": "aleyTYvQjKT4QAcFztyYNHVC",
        "status": "created",
        "date_created": "2024-12-03T00:01:32.580491Z"
    },
    {
        "uid": "alebV6fWMgUARPmCBJDKQGKQ",
        "status": "complete",
        "date_created": "2024-12-02T23:59:47.426752Z"
    }
]

1. Make a POST request to /api/v2/access-logs/export and verify you receive a 202 Accepted with this response:

[
    "status: created"
]

1. Logout and try to access the endpoint. Verify you get receive a 401 Unauthorized
   with this response:

{
    "detail": "Authentication credentials were not provided."
}

1. Login as a regular user and access the endpoint. Verify you receive a 403 Forbidden with this response:

{
    "detail": "You do not have permission to perform this action."
}

Test /api/v2/access-logs/me/export

Follow the same testing instructions above but skip number 7 as both superusers and regular users have the same access to the endpoint.

🟢 Also verify that making a POST request on both endpoints should now generate an email with the follow format:

kpi_worker-1      | MIME-Version: 1.0
kpi_worker-1      | Content-Transfer-Encoding: 7bit
kpi_worker-1      | Subject: Access Log Report Complete
kpi_worker-1      | From: webmaster@localhost
kpi_worker-1      | To: test@test.com
kpi_worker-1      | Date: Wed, 27 Nov 2024 19:38:29 -0000
kpi_worker-1      | Message-ID: <173273630990.23.10232391233968451994@948bfe8772ce>
kpi_worker-1      | 
kpi_worker-1      | Hello test,
kpi_worker-1      | 
kpi_worker-1      | Your report is complete: http://kf.kobo.local:8080/private-media/test/exports/access_logs_export-test-2024-11-27T193829Z.csv
kpi_worker-1      | 
kpi_worker-1      | Regards,
kpi_worker-1      | KoboToolbox

[rgraber]

We can make this more declarative/django-y if we use 2 different endpoints (like we do for viewing access logs).
We can use filter_backends and permission_classes like we do in the AllAccessLogViewSet and AccessLogViewSet to handle filtering down to the correct user and only allowing super users. That should allow us to get rid of a lot of the if-elses and having to check the request path, which is a little brittle (sometimes we might want to change the url of something without changing its functionality).

Also the endpoints need documentation :)

[rgraber]

No 404 here. An empty list is not an error response

[rgraber]

Couple small things

[rgraber]

Doesn't this mean we'll only get a superuser's tasks even if they hit the all endpoint? Not a huge deal if that ends up being the functionality since it's optional anyway but we should make sure we document the correct behavior

[rgraber]

non-blocking nit, since this doesn't technically test that the task started, only that the request suceeded

Suggested change

	def test_export_for_user_commences(self):
	def test_export_for_user_returns_success(self):

[rgraber]

same as above

[rgraber]

This is a tiny bit risky since we don't know exactly when the task will finish. Maybe test status in ['created', 'processing', 'complete']?

[rgraber]

to make this test more unit-y, I think we should manually create a task with AccessLogExportTask.objects.create(...). That way, we're only testing the list functionality and not the create functionality as well, since that's already tested.

[rgraber]

Suggested change

	def test__superuser_create_export_task_on_post(self):
	def test_superuser_create_export_task_on_post(self):

[rgraber]

same as previous test, the test should pass if the status is 'processing' or 'created'

[rgraber]

error message suggestions and one thing on a test

[rgraber]

LGTM

[rgraber]

nit (nonblocking)

Suggested change

	self.assertEqual(task.get_all_logs, False)
	self.assertFalse(task.get_all_logs)