chore: settle product naming across app, widget and deployments

One word everywhere: ReplyPier in UI copy, package and image names, the
replypier.site domains (app/api/docs/help), REPLYPIER_* settings and the
--rp-* design tokens.

- public widget API is window.ReplyPier with replypierId / replypierBaseUrl /
  replypierConfig / replypierToken, loader at webclient/replypier.min.js;
  both bundles rebuilt from source
- NOTICE, llms.txt, CONTRIBUTING, HELP_CENTER_INFRA and the demo runtime
  config rewritten; the demo config ships no third-party keys
- migration adds the ReplyPier managed model value to the AI model enum
- local compose project, database, role, volume and Docker network carry the
  same name

backend/app/models/investigation.py

@@ -1,5 +1,5 @@
 """
-Copyright 2024-2026 ChatterMate
+Copyright 2024-2026 ReplyPier
 
 Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
@@ -236,7 +236,7 @@ class TicketProposal(Base):
     """Autonomy L2: a resolution the AI proposes and a human decides on.
     Approval resolves the ticket and notifies the customer; a rejection can
     feed a refined investigation run (the reason becomes its context_note).
-    ChatterMate never executes infrastructure changes — approval records the
+    ReplyPier never executes infrastructure changes — approval records the
     decision, humans/runbooks perform any mutation."""
     __tablename__ = "ticket_proposals"