feat: support config store and redis configuration optional in mcp server

[Jing-ze]

Ⅰ. Describe what this PR did

support config handler and store in mcp server
feat: support mcp server redis configuration optional
fix bug of redis not enabled response body
feat: add internal IP check for config path access
update mcp-server.so to golang-filter.so
fix: support panic recover in go routine and pprof in mcp server

Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?

Ⅳ. Describe how to verify it

Ⅴ. Special notes for reviews

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 16.32653% with 41 lines in your changes missing coverage. Please review.

Project coverage is 43.59%. Comparing base (ef31e09) to head (0aa5bdc).
Report is 435 commits behind head on main.

Files with missing lines	Patch %	Lines
pkg/ingress/kube/configmap/mcp_server.go	16.32%	40 Missing and 1 partial ⚠️

❌ Your patch status has failed because the patch coverage (16.32%) is below the target coverage (50.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2035      +/-   ##
==========================================
+ Coverage   35.91%   43.59%   +7.68%     
==========================================
  Files          69       79      +10     
  Lines       11576    12754    +1178     
==========================================
+ Hits         4157     5560    +1403     
+ Misses       7104     6846     -258     
- Partials      315      348      +33     

Files with missing lines	Coverage Δ
pkg/ingress/kube/configmap/mcp_server.go	39.85% <16.32%> (ø)

... and 74 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[johnlanni]

The overall logic is fine, but the mcp server logic at the uid granularity needs to be completely decoupled and controlled through an independent configuration item, such as enableUserLevelServer: true