fix(sitemanage): drop non-existent verbose property on CXF LoggingFeature bean

[natechadwick-intsof]

Summary

Drops the non-existent verbose property from the cxfLoggingFeature Spring bean in projects/sitemanage/.../sitemanage-beans.xml. Without this fix the Rhythmyx webapp fails to start: Spring throws NotWritablePropertyException on the bean, the root ApplicationContext fails to refresh, and Jetty reports the context as UNAVAILABLE.

Why

org.apache.cxf.feature.LoggingFeature in CXF 3.5.11 exposes only two setters — setLimit(int) and setPrettyLogging(boolean) — plus the LoggingFeature(String, String, int, boolean, boolean) constructor (inLocation, outLocation, limit, prettyLogging, showBinary). The verbose flag was removed when the inner LoggingFeature$Portable class was introduced in 3.5.x. The sitemanage-beans.xml bean added by the T2.3 hardening PR (#169, issue #168) was written against the older 3.4.x API and still set verbose=false. Verified by javap on cxf-core-3.5.11.jar:

public class org.apache.cxf.feature.LoggingFeature extends
    org.apache.cxf.feature.DelegatingFeature<...LoggingFeature$Portable> {
  ...
  public void setLimit(int);
  public int getLimit();
  public boolean isPrettyLogging();
  public void setPrettyLogging(boolean);
}

Cascade on startup

cxfLoggingFeature bean (verbose setter missing)
  -> NotWritablePropertyException
    -> rest-jax-rs bean fails (references cxfLoggingFeature)
      -> Spring root context fails to refresh
        -> Rhythmyx webapp UNAVAILABLE

CI_Home and EI_Home start fine because they don't share the root context.

What stays

limit=4096 and prettyLogging=false remain in the bean. They were the actual safety controls the original analysis intended:

• limit=4096 caps the bytes the interceptor writes; the rest is truncated.
• prettyLogging=false keeps the output single-line, faster, smaller.

The original analysis doc (docs/.../issues/168-t2-3-cxf-logging-hardening.md) is updated in this PR with a post-merge revision note so the verbose property isn't re-added by a future reader.

Verification

• python3 -c "import xml.etree.ElementTree as ET; ET.parse('.../sitemanage-beans.xml')" -> well-formed.
• After rebuild + deploy: Rhythmyx webapp reaches AVAILABLE; the cxfLoggingFeature / rest-jax-rs / NotWritablePropertyException chain is gone from jetty/base/logs/server.log.

Out of scope

• The other WARN lines in the startup log (X1_GENERAL_EXTERNAL_ENTITIES_FEATURE not recognized, Ignored arg <Arg name="threadpool">) are addressed separately. The X1/X2 noise is fixed in fix(utils): drop dead Xerces-1/Xerces-2 feature URIs from default DocumentBuilderFactory #205 (branch bugfix/135-xerces-x1x2-feature-removal). The threadpool warning comes from the upstream Jetty 9.4.58 distribution and is pre-existing.

Refs #168

Co-Authored by Mavis Mavis-Code using MiniMax-M3 with agent mavis.