custom access logs for default site

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
  • Yes
• Are you sure you're not using someone else's docker image?
  • Yes
• Have you searched for similar issues (both open and closed)?
  • Yes

Describe the bug
When changing default log location and type this setting does not apply to the default site and there is no way to change this, so for purposes like logging all the AI crap that will make requests like /.git/ is actually useless since everything will end in the fallback_log with its format ignoring actually the http_top.conf and server_proxy.conf files.

My actual solution was to set as the default page a custom one and then edit /data/nginx/default_host/site.conf, still if you edit the custom page from the web interface all changes will be lost.

Nginx Proxy Manager Version
v2.12.6

To Reproduce
For example my server_proxy.conf looks like this:

access_log /data/logs/all_proxy_access.log json_analytics;
error_log /data/logs/all_proxy_error.log warn;

(obv you have to define json_analytics log format)

but the default site logs keeps falling under the default fallback_access.log file and with the default format (not the one specified)

Expected behavior
that the default page respects the correct configuration or another way to tell to NPM "use this configuration", don't override/ignore it with the default one

Operating System
Via docker on opensuse virtualized on Proxmox

Inspect how the default site is generated, beginning with /data/nginx/default_host/site.conf and the server_proxy.conf and http_top.conf settings described. Reproduce the issue with the provided access_log and error_log configuration, then verify that the default site's paths and log format are respected and are not overwritten after web edits.