New linter rule for private bicep registry modules "use-latest-module-versions"

**Is your feature request related to a problem? Please describe.**
```text
demo-registry.private.registry.io/bicep/gateway:1.0.0
demo-registry.private.registry.io/bicep/gateway:1.1.1
demo-registry.private.registry.io/bicep/gateway:1.1.2
```
Above version of bicep module present in registry.
currently this module is consumed by other bicep files in differnt places.
```
module gateway 'br:demo-registry.private.registry.io/bicep/gateway:1.1.1' {

}
```
Currently there is no way if these bicep using older bicep registry version?

**Describe the solution you'd like**
If we have linter rule in bicepconfig.json something like use-latest-module-versions which checks on registry if we have higher version of module available in remote registry then it should give warning or bicep build failure on level 'error'.

```
"use-latest-module-versions": {
"level": "warning"
}
```

Start with the linter configuration example in bicepconfig.json and the described private registry module references. Determine how a rule could compare consumed versions with higher versions in the registry and report the configured warning or error; done means older module references are detected at the requested severity.

Written by the indexing model from the issue text.