Allow resource ID as deployment scope within module for increased flexibility

[JayDoubleu]

Currently, bicep does not allow using a resource ID as a deployment scope within a module. Instead, it only accepts the bicep symbolic name. This means that I have to specifically call out the "existing" resource type and only then can I reference it in another resource, such as diagnostic settings.

This limitation makes it difficult to create a single diagnostic settings module that can handle different resource types. A potential solution would be to allow the scope within a module to be a resource ID as a string or enable the usage of a function such as resource('stringResourceId') as a scope for other resource deployments.

By implementing this feature, users would be able to create more flexible and reusable modules for managing diagnostic settings and other resources in terraform like style.

[alex-frankel]

Closing as dup of #2245/#2246