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/util/ServerBootConfig.cs

@@ -28,6 +28,9 @@ namespace AyaNova.Util
         internal const string CUSTOMER_NOTIFICATION_ATTACHED_REPORT_RENDER_USERNAME =
             "CUSTOMER NOTIFICATION - NO USER";
 
+        //case 4632: true when running inside IIS (in-process hosting), where the report page's API calls are relayed (ReportApiRelay)
+        internal static bool HOSTED_IN_IIS { get; set; }
+
         //############################################################################################################
 
         //############################