There should be a command/context menu to open the bicepconfig.json file corresponding to the current bicep file

It could be in the current folder or any parent folder, or if non exists, we could query if they want to create one

Start by locating the command/context-menu handling for a current Bicep file and the logic that finds bicepconfig.json in the current or parent folders. Done means the menu opens the matching configuration file and, when none exists, queries whether to create one.

Written by the indexing model from the issue text.