Add support for defining required Dev Proxy version in project settings for team scenarios

[garrytrinder]

Problem

Currently, Dev Proxy detects when a schema version in a config file does not match the installed version and offers to upgrade using Copilot. This works well for individual developers but creates gaps for teams, as members can end up using different Dev Proxy versions unintentionally. This can lead to unpredictable behavior, troubleshooting difficulties, and configuration drift across the team.

Proposed Feature

Introduce a mechanism to define and enforce the required Dev Proxy version at the project/workspace level. This would help ensure that all team members are using the same Dev Proxy version, eliminating version-related surprises and making troubleshooting more consistent.

[waldekmastykarz]

We should look into using dotnet tool for this. dotnet tool install (without the --global) switch could be a way to support local installs