Completion for module MCR/ACR references is very dependent on the cursor being at particular parts of the string
top-level
module a '<cursor>': works as expected
module a 'b<cursor>': no MCR/ACR completion (expecting 'br/')
module a 'br<cursor>': no MCR/ACR completion (expecting 'br/')
alias
module a 'br/<cursor>': works as expected
module a 'br/p': no MCR/ACR completion (expecting 'br/public:')
module a 'br/p': no MCR/ACR completion (expecting 'br/public:')
modulename
module a 'br/public:<cursor>': works as expected
module a 'br/public:app<cursor>': no completion (expected 'br/public:app/dapr-containerapp:', 'br/public:app/dapr-containerapps-environment:')
module a 'br/public:app/<cursor>': no completion (expected 'br/public:app/dapr-containerapp:', 'br/public:app/dapr-containerapps-environment:')
version
module a 'br/public:app/dapr-containerapp:<cursor>': works as expected
module a 'br/public:app/dapr-containerapps-environment:1<cursor>': no completion
Examples:

@StephenWeatherford, can we close this?
No, this is not fixed.