Better handling of resource conflicts

When creating some resources, conflicts are encountered that require explicit sequencing with DependsOn.

2 examples of this are;

1. Adding peerings to 2 vnets at the same time ([example](https://github.com/Gordonby/BicepLessons/blob/main/Conflicts.md#vnet-peers)).
2. Creating multiple NSG Flow Logs on the same Network Watcher ([example](https://github.com/Gordonby/BicepLessons/blob/main/Conflicts.md#nsg-flow-logs))

Whilst this is just part of the way Azure works, i'm sure that Bicep could augment the deployments to save me having to lean on DependsOn quite so often.

In the first instance, the linter could raise a problem to alert me.
I'd also be quite happy if bicep added the dependsOn for me 😄

Read the linked VNet peering and NSG Flow Logs conflict examples first, then compare the reported behavior with how explicit DependsOn is currently used. Define whether the desired outcome is a linter diagnostic, automatic dependency insertion, or both, and verify that the chosen behavior prevents these deployment conflicts without requiring manual sequencing.

Written by the indexing model from the issue text.