Updating our internal dependencies (copilot, bicep, gh cli, possibly others) as part of a regular automated cadence

There are two parts to this:
- The mechanical update itself. I think there's already a skill to do this, it just requires a person to go in and create the PR. This might be a simple start, but we'll probably want to convert this into a script so the execution is consistent.
- The rule for when we allow for an automated update. New patch version seems absolutely fine, but depending on the deps history (ie, stable minor releases, etc..) we might need to change it up a bit.

This is probably small enough that it doesn't warrant a big design discussion, but would like feedback from the team. @vhvb1989 , can you tell me if there is any nuance or details that I need to consider before we start?