Make API nginx log once per request

[obulat]

Fixes

Fixes #3126 by @obulat

Description

While reviewing #3108, I found a way to make Nginx log only once, using the json style described in the nginx.conf.template, to the frontend nginx container.
This PR adds the same changes to the API nginx container.

Testing Instructions

Rebuild the api and nginx containers (use just recreate, or delete the openverse-nginx image using a GUI and run just up), and access the API through the nginx proxy: http://0.0.0.0:50270/v1/images/?q=cat

Check the nginx container (image name is openverse-nginx) logs: there should only be one json formatted log per request, and not two logs per request as described in the issue.
Here's the logs I saw after opening the api home page and then searching for "cat" images:

{"time_local":"11/Oct/2023:15:53:14 +0000","remote_addr":"192.168.247.1","remote_user":"","request":"GET /v1/ HTTP/1.1","status": "200","host_header": "0.0.0.0","body_bytes_sent":576,"request_time":"0.016","http_referrer":"","http_user_agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36","upstream_response_time":0.016,"http_x_forwarded_for":""}
{"time_local":"11/Oct/2023:15:53:14 +0000","remote_addr":"192.168.247.1","remote_user":"","request":"GET /v1/schema/ HTTP/1.1","status": "200","host_header": "0.0.0.0","body_bytes_sent":84591,"request_time":"0.112","http_referrer":"http://0.0.0.0:50270/v1/","http_user_agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36","upstream_response_time":0.112,"http_x_forwarded_for":""}
{"time_local":"11/Oct/2023:15:53:18 +0000","remote_addr":"192.168.247.1","remote_user":"","request":"GET /v1/images/?q=cat HTTP/1.1","status": "200","host_header": "0.0.0.0","body_bytes_sent":8561,"request_time":"0.486","http_referrer":"","http_user_agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36","upstream_response_time":0.486,"http_x_forwarded_for":""}

Checklist

• My pull request has a descriptive title (not a vague title likeUpdate index.md).
• My pull request targets the default branch of the repository (main) or a parent feature branch.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.
• I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[sarayourfriend]

Cool!

[krysal]

Perhaps I'm missing some steps, are those the full instructions? I remember some slightly different steps to test nginx locally but I can't find them exactly.

Also, I notice now there are two Nginx services under the api profile, proxy and nginx, are both serving the same/similar goals? Can't they be combined?

I'm requesting changes for clarification on how to test this and responses. The questions go to @sarayourfriend and @dhruvkb too in case you know, given you have worked more closely with these services.

[sarayourfriend]

The "proxy" container is leftover for SSL testing locally. Its presence continues to be confusing to lots of people, and @dhruvkb and I have talked about getting rid of it: I don't know if there's an issue though. @dhruvkb do you remember/can you create an issue with whatever we decided, if you remember that?

[openverse-bot]

Based on the medium urgency of this PR, the following reviewers are being gently reminded to review this PR:

@krysal
@dhruvkb
This reminder is being automatically generated due to the urgency configuration.

Excluding weekend¹ days, this PR was ready for review 7 day(s) ago. PRs labelled with medium urgency are expected to be reviewed within 4 weekday(s)².

@obulat, if this PR is not ready for a review, please draft it to prevent reviewers from getting further unnecessary pings.

Footnotes

1. Specifically, Saturday and Sunday. ↩

2. For the purpose of these reminders we treat Monday - Friday as weekdays. Please note that the operation that generates these reminders runs at midnight UTC on Monday - Friday. This means that depending on your timezone, you may be pinged outside of the expected range. ↩