Add command to dump dynamic config values (#421)

[vaibhavyadav-dev]

What changed?

Added an admin command that dump all frontend dynamic config values,

Why?

Operators currently cannot easily inspect frontend runtime dynamic configuration, dumping values aids troubleshooting, incident response, and verification after config changes.

How did you test it?

• [x] built
• [x] run locally and tested manually
• [x] covered by existing tests
• [x] added new unit test(s)
• [ ] added new functional test(s)

Closes #421

[vaibhavyadav-dev]

@bergundy I think It's better to add DefaultKey in this handler .

Do let me know what you think, Thanks

[vaibhavyadav-dev]

Thanks for the review @dnr I have a question about the approach since It doesn't work for settings with multiple constrained defaults, and inserting defaults at load time is bad.

I'm considering two alternatives.

• Only display values that are explicitly configured in the dynamic config file. If a setting isn't present, don't show it.
• Retrieve defaults at display time from the registry based on the actual constraints being queried.

Which approach would you prefer? I'm leaning toward first one as it's simpler and provides value for operators troubleshooting config issues.