[Feature Request] Don't require specifying Flutter version in VS Code dart.flutterSdkPath config

[zeshuaro]

Before creating a feature request make sure the suggestion fit within our principles

Is your feature request related to a problem? Please describe.
I recently started to migrate my projects to fvm v3. However, I noticed that v3 now requires the following config for VS Code integration, which involves specifying the Flutter version

{
  "dart.flutterSdkPath": ".fvm/versions/3.22.2"
}

The problem I'm facing is that I also use Renovate to automatically update all my dependencies, which includes updating my project Flutter version. This has been fine with fvm v2 as it simply updates .fvm/fvm_config.json with the new Flutter version (sample PR).

While Renovate has already been updated to support .fvmrc in v3, I don't believe it supports updating the VS Code config, as that's probably out-of-scope for a dependency management tool. So now with fvm v3, my Renovate workflow no longer works as the VS Code config also needs to be updated.

Describe the solution you'd like
Don't require specifying Flutter version in VS Code dart.flutterSdkPath config, so that users don't have to worry about updating this config when they update Flutter version.

Describe alternatives you've considered
A GitHub actions step, which will run after the Renovate PR is created, to parse .fvmrc and read the latest version, then update it in VS Code config. But I'm hoping to avoid doing this.

Additional context
N/A