Parameter/property defined as any type throws error when using statement referes to container registry module

[slavizh]

Bicep version
Bicep CLI version 0.38.33 (6bb5d5f)

Describe the bug
This issue appears only when you have bicepparam file with using statement pointing to container registry module if you use the same module but point it to local bicep file the error goes away. This is not the first time when there are differences between pointing to local module and pointing to container registry module. Due to that I think there should be some general action taken into account to prevent this from happening in the future.

To Reproduce
Steps to reproduce the behavior:
Should be reproducible by having main.bicep published as module:

param foo any

and after that pointing the bicepparam file to the module in the registry

using 'br:<path to container registry>'

param foo = 'test'

Here is screenshots from VSC:

The property "" expected a value of type "error" but the provided value is of type "'property value'".bicepBCP036

if you do

main.json

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "metadata": {
    "_generator": {
      "name": "bicep",
      "version": "0.38.33.27573",
      "templateHash": "16900384022505884854"
    }
  },
  "parameters": {
    "foo": {}
  },
  "resources": []
}

bicepparam

using 'main.json'

param foo = 'test'

you get the same error

Additional context
Add any other context about the problem here.

[slavizh]

Here is another working item where there is difference: #17947 . There were others in the past that are closed.

[slavizh]

@jeskew Jonny can you have a look and if possible to release a bicep cli fix as it makes any not usable for majority of use cases.