Enable Configuration Management (config) "updateTrigger" when enabling tracing

[kinueng]

A prerequisites for using WebSphereLibertyTrace custom resource

The Liberty server must allow configuration drop-ins. The following configuration must not be set on the server. Otherwise, a WebSphereLibertyTrace operation does not work on the server.

<config updateTrigger="disabled"/>

https://www.ibm.com/docs/en/was-liberty/base?topic=resources-webspherelibertytrace-custom-resource#cfg-r-crd-wlt__trace-prq

<config updateTrigger="disabled"/> is set to reduce idle CPU time

• https://openliberty.io/docs/latest/performance-tuning.html#idle_cpu

My request

1. Allow for servers to always have <config updateTrigger="disabled"/> for the performance gains
2. When WebSphere Liberty Operator enables trace on a Liberty server with <config updateTrigger="disabled"/>, WLO will remove <config updateTrigger="disabled"/> from the server to allow for tracing to work.
3. When WLO turns off trace on the server, <config updateTrigger="disabled"/> is enabled again to get the performance gains.