ZCU-DATA/filter config.json before exposing it

[jr-rk]

Phases	MP	MM	MB	MR	JM	Total
ETA	0	0	0	0	0	0
Developing	0	0	0	0	0	0
Review	0	0	0	0	0	0
Total	-	-	-	-	-	0
ETA est.						0
ETA cust.	-	-	-	-	-	0

Problem description

Eliminating the security risk of exposing sensitive server-side configuration data to the frontend, by filtering the config object to only include client-necessary settings before writing to config.json.
based on #1067

[Copilot]

Pull Request Overview

This PR introduces a security improvement by sanitizing the configuration data exposed to the frontend. Instead of writing the entire appConfig object to the public config file, it creates a filtered publicConfig object that only includes client-side configuration properties.

Key Changes:

• Created a sanitized publicConfig object that explicitly includes only necessary frontend properties
• Excluded server-side sensitive configuration (UI server host/port/ssl, REST server host/port/ssl, rate limiter settings, actuators config)
• Maintained all frontend-required features (themes, languages, forms, submission, etc.)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.