Support gradual rollout flag for realtime updates

[Mishenevd]

Backend can now enable realtime updates per-account via an enabledFeatures list on the config response, ahead of AIKIDO_FEATURE_SSE being set locally. SSE starts if either is true.

Mirrors the change already merged in firewall-node and firewall-ruby. Feature name is realtime_updates, matching the backend.

APIResponse keeps an 11-arg constructor defaulting enabledFeatures to empty, so the ~25 existing call sites in tests are untouched.

Testing:

• Unit tests on ServiceConfiguration/ServiceConfigStore: defaults to false, true when present, false again once removed, false for an unrelated feature name

[codecov]

Codecov Report

❌ Patch coverage is 23.07692% with 10 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
...aikido/agent_api/storage/ServiceConfiguration.java	0.00%	4 Missing ⚠️
...aikido/agent_api/background/BackgroundProcess.java	0.00%	3 Missing ⚠️
...v/aikido/agent_api/storage/ServiceConfigStore.java	0.00%	3 Missing ⚠️

📢 Thoughts on this report? Let us know!

[aikido-pr-checks]

Summary by Aikido

Security Issues: 0	Quality Issues: 0	Resolved Issues: 0

⚡ Enhancements

• Stored enabledFeatures in ServiceConfiguration and updated config parsing logic
• Added ServiceConfiguration.isRealtimeUpdatesEnabled check to expose feature state
• Made BackgroundProcess start SSE when flag or server-enabled feature was present
• Extended APIResponse with enabledFeatures and added backward-compatible constructor

^{More info}