Centralized bicepconfig.json within Bicep Registry

When it comes to leveraging Bicep there will be use cases where a centralized team is creating the modules and other "turn key" resources. This way they can be consumed by developers locally or within their own pipelines. Having the ability to create a centralized bicepconfig.json which can be maintained and provided for best practice.

A great solution for this would be to host this within a Bicep Registry (Public or Private) and be able to reference to it. That way best practices can standardized there wouldn't be a need to have dozens of bicepconfig.json files in various repos.

Rough Example...
./bicepconfig.json > reference br:myRegistry:bicepconfig.json (singular or many)
./bicepconfig.json > can also have custom rules too (but can't conflict with any referenced bicepconfig.json files)

No implementation files or tests are named in the issue. Start by investigating how bicepconfig.json is currently loaded and how Bicep Registry references are resolved, then clarify whether centralized configurations may be singular or multiple and how local custom rules should merge or conflict. Done should include an agreed behavior and corresponding support for registry-hosted configuration.

Written by the indexing model from the issue text.