case 4632 - reports render under IIS: the report page's API calls are relayed by the server

Inside IIS (in-process) AyaNova has no port of its own, so the report page
could not reach the API: user reports called http://127.0.0.1:<request port>
(reset on https), notification reports 127.0.0.1:7575 (refused). Under IIS the
page's requests under the API URL are now intercepted and made by the server
(util/ReportApiRelay.cs) to the local address and port a user's request
arrived on, with its host name and scheme; notification reports use the
latest signed-in request, else the override. Outside IIS nothing changes.
The notification token check requires a request from this machine, no longer
host 127.0.0.1. Manual (IIS install, override page) and changelog updated.
Deferred: emailed PDF content type application/pdf/pdf.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

server/AyaNova/generator/CoreJobCustomerNotify.cs

@@ -336,7 +336,9 @@ namespace AyaNova.Biz
                                     ServerBootConfig.AYANOVA_REPORT_RENDERING_TIMEOUT
                                 ),
                                 API_URL,
-                                ServerBootConfig.CUSTOMER_NOTIFICATION_ATTACHED_REPORT_RENDER_USERNAME
+                                ServerBootConfig.CUSTOMER_NOTIFICATION_ATTACHED_REPORT_RENDER_USERNAME,
+                                //case 4632: inside IIS nothing listens on that port, the API calls are relayed to where users' requests arrive
+                                ReportApiRelay.ForBackgroundRender()
                             );
                             if (jobid == null)
                             {