Feature Request: Add Support for Specifying `bicepconfig.json` Settings in the Bicep Playground

### Summary

I would like to propose an enhancement to the Bicep Playground that would allow users to specify settings from `bicepconfig.json` directly within the playground interface. The Bicep Playground is a valuable tool for developers to view Bicep and equivalent JSON side by side, enabling a clear comparison of the implementations of the same infrastructure. By introducing the ability to adjust `bicepconfig.json` settings in the playground, users can further tailor their development experience to better suit their needs.

### Rationale

Incorporating the ability to specify `bicepconfig.json` settings directly in the Bicep Playground would provide several benefits:

- **Enhanced Customization**: Users would be able to experiment with different configurations easily, seeing the effects in real-time without the need to adjust files locally.
- **Improved Accessibility**: New users or those evaluating Bicep could explore advanced features without setting up a complete development environment, lowering the barrier to entry.
- **Consistency and Convenience**: Allowing `bicepconfig.json` customization in the playground aligns with the flexibility and user-centric design philosophy of Bicep, offering a more consistent and convenient development experience across different environments.

### Conclusion

The addition of `bicepconfig.json` settings customization in the Bicep Playground would be a valuable enhancement, aligning with the tool's goal of providing a versatile and user-friendly platform for infrastructure as code development. This feature would not only improve the playground's functionality but also serve as an educational tool for demonstrating the impact of various configurations on Bicep deployments.

I hope the Bicep maintainers team considers this feature request, as I believe it would significantly benefit the Bicep community.

Thank you for your time and consideration.

The issue mentions the Bicep Playground and bicepconfig.json, but names no source files, tests, or entry points. Start by reviewing how the playground currently handles configuration and which bicepconfig.json settings are supported. Define the in-scope settings and interaction before implementing; done means users can change them and see their effects in the side-by-side output.

Written by the indexing model from the issue text.