Add v2 client-side PDF text editor (#6500)

# Description of Changes

<!--
Please provide a summary of the changes, including:

- What was changed
- Why the change was made
- Any challenges encountered

Closes #(issue_number)
-->

---

## Checklist

### General

- [ ] I have read the [Contribution
Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md)
- [ ] I have read the [Stirling-PDF Developer
Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md)
(if applicable)
- [ ] I have read the [How to add new languages to
Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md)
(if applicable)
- [ ] I have performed a self-review of my own code
- [ ] My changes generate no new warnings

### Documentation

- [ ] I have updated relevant docs on [Stirling-PDF's doc
repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/)
(if functionality has heavily changed)
- [ ] I have read the section [Add New Translation
Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags)
(for new translation tags only)

### Translations (if applicable)

- [ ] I ran
[`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md)

### UI Changes (if applicable)

- [ ] Screenshots or videos demonstrating the UI changes are attached
(e.g., as comments or direct attachments in the PR)

### Testing (if applicable)

- [ ] I have run `task check` to verify linters, typechecks, and tests
pass
- [ ] I have tested my changes locally. Refer to the [Testing
Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#7-testing)
for more details.

Author: Frooodle

app/core/build.gradle

@@ -306,6 +306,9 @@ tasks.register('copyFrontendAssets', Copy) {
         // Exclude files that conflict with backend static resources
         exclude 'robots.txt'  // Backend already has this
         exclude 'favicon.ico' // Backend already has this
+        // Backend ships its own NotoSans-Regular.ttf here and it is git-tracked;
+        // letting the editor's copy win would dirty the source tree on every build.
+        exclude 'fonts/NotoSans-Regular.ttf'
     }
     into resourcesStaticDir
     duplicatesStrategy = DuplicatesStrategy.INCLUDE  // Let frontend overwrite when needed

app/core/src/main/java/stirling/software/SPDF/controller/api/PdfTextEditorCharcodeController.java

@@ -154,7 +154,8 @@ public String detectFontFlavor(byte[] fontBytes) {
             return "otf";
         }
         if (signature == 0x74746366) {
-            return "cff";
+            log.debug("[FONT-DEBUG] TrueType Collection ('ttcf') font program is unsupported");
+            return null;
         }
         return null;
     }
@@ -175,7 +176,8 @@ public String detectTrueTypeFormat(byte[] data) {
             return "otf";
         }
         if (signature == 0x74746366) {
-            return "cff";
+            log.debug("[FONT-DEBUG] TrueType Collection ('ttcf') FontFile2 is unsupported");
+            return null;
         }
         return null;
     }

app/core/src/main/java/stirling/software/SPDF/service/pdfjson/PdfJsonFontService.java

@@ -15,26 +15,63 @@
         <encoder>
             <pattern>%d %p %c{1} [%thread] %m%n</pattern>
         </encoder>
-        <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
-            <fileNamePattern>${LOG_PATH}/auth-%d{yyyy-MM-dd}.log.gz</fileNamePattern>
+        <!-- SizeAndTime, not Time alone: the size trigger is what stops a
+             runaway logger filling the disk (see GENERAL appender note).
+             Archives are gzipped, so 64 MB of them holds far more than a
+             day. Worst case on disk is one 100 MB live file plus the cap. -->
+        <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">
+            <fileNamePattern>${LOG_PATH}/auth-%d{yyyy-MM-dd}.%i.log.gz</fileNamePattern>
+            <maxFileSize>100MB</maxFileSize>
             <maxHistory>7</maxHistory>
             <totalSizeCap>64MB</totalSizeCap>
         </rollingPolicy>
     </appender>
 
-    <!-- Rolling File Appender for General Logs -->
+    <!-- Rolling File Appender for General Logs
+
+         Why SizeAndTimeBased + totalSizeCap: a previous build of the v2 PDF
+         text editor's reverse-CMap probe loop triggered PDSimpleFont to emit
+         one "No Unicode mapping for .notdef" WARN per probed charcode per
+         font per request. With TimeBasedRollingPolicy alone there was no
+         size ceiling; info.log grew to 1.4 GB in a single day before the JVM
+         choked. The class-level silencer fixes the specific offender, but
+         this size cap is the defence-in-depth: any future logger that
+         floods unexpectedly will roll + auto-delete instead of starving
+         disk + Jetty threads. -->
     <appender name="GENERAL" class="ch.qos.logback.core.rolling.RollingFileAppender">
         <file>${LOG_PATH}/info.log</file>
         <encoder>
             <pattern>%d %p %c{1} [%thread] %m%n</pattern>
         </encoder>
-        <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
-            <fileNamePattern>${LOG_PATH}/info-%d{yyyy-MM-dd}.log.gz</fileNamePattern>
+        <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">
+            <fileNamePattern>${LOG_PATH}/info-%d{yyyy-MM-dd}.%i.log.gz</fileNamePattern>
+            <maxFileSize>100MB</maxFileSize>
             <maxHistory>7</maxHistory>
             <totalSizeCap>256MB</totalSizeCap>
         </rollingPolicy>
     </appender>
 
+    <!-- Suppress PDFBox PDSimpleFont's per-charcode .notdef WARN.
+
+         Required by the v2 PDF text editor's `buildReverseUnicodeMap`
+         which DELIBERATELY iterates every charcode in 0..0xFFFF to
+         discover the encoding-to-Unicode map of an embedded subset
+         font. For any subset font ~99% of those probes hit .notdef,
+         and the default WARN level for those misses turned info.log
+         into a 1.4 GB monster overnight.
+
+         This declarative logback entry is the SOLE mechanism: it is
+         visible to ops and revertable via configuration. An earlier
+         build also mutated this logger's level from a static block in
+         PdfTextEditorCharcodeController, which silenced the same
+         warnings JVM-wide with no trace in any config file - that
+         static block has been removed in favour of this entry. -->
+    <logger name="org.apache.pdfbox.pdmodel.font.PDSimpleFont"
+            level="ERROR" additivity="false">
+        <appender-ref ref="CONSOLE"/>
+        <appender-ref ref="GENERAL"/>
+    </logger>
+
     <!-- Root Logger -->
     <root level="INFO">
         <appender-ref ref="CONSOLE"/>

app/core/src/main/resources/logback.xml

@@ -57,6 +57,8 @@ class ToolIODeclarationCoverageTest {
                     // documents.
                     "/api/v1/convert/pdf/text-editor",
                     "/api/v1/convert/text-editor/pdf",
+                    // Charcode lookup for the v2 editor: returns glyph mappings, not a document.
+                    "/api/v1/general/pdf-text-editor",
                     // Signing sessions, certificate checks and hardware token enumeration; the
                     // signing tool itself is /api/v1/security/cert-sign, which is declared.
                     "/api/v1/security/cert-sign/sessions",