Issue Summary

When analytics is disabled via the UI, or via REST API, that change does not get propogated to the other nodes in the cluster, and therefore only takes effect on the single node that received the request. 

This is a problem, because a customer would expect when disabling analytics that analytics is completely disabled. Actually it looks like it is only disabled partially. 

Steps to Reproduce

1. Jira Admin -> System -> Analytics -> Disabled -> Save (warning! JRASERVER-78791)
   or

   curl http://your_jira_node/rest/analytics/1.0/config/enable -u admin:password -X 'PUT' -H 'content-type: application/json' --data-raw '{"analyticsEnabled":false}' 

2. Connect to another node, and visit the same Analytics configuration page

Expected Results

1. Analytics is now disabled across the cluster - all nodes show "Disabled"

Actual Results

1. Analytics is only disabled on the node where "Disabled" was clicked. Other nodes are still "Enabled":
   • The UI shows "enabled"
   • Logs are actively written to the analytics-logs directory

Workaround

Repeat the procedure on all nodes in the cluster