Should be decided by a PM and needs corresponding fixes for Flutter Tool, VSCode and DevTools (if it changes from vm-uri).

When creating a configuration to attach to a running Flutter application the VM URI is called observatoryUri this will be confusing as DevTools is calling this vm-uri and Flutter tool will also be calling something else hopefully 'VM Uri'. We need to coordinate with Flutter too on a name.

• DevTools CLI uses --vm-uri

• Flutter tool calls it An Observatory debugger and profiler e.g.,

An Observatory debugger and profiler on AOSP on IA Emulator is available at: http://127.0.0.1:34637/OIt9yrpqmNE=/

Should we call it The VM Uri to attach, debug or profile at http://127.0.0.1:33933/aAqCdEkfG4A=/?

• In VSCode's launch.json the name is observatoryUri to attach to a running Flutter application:

    "version": "0.2.0",
    "configurations": [
        // Attach to a running test.
        {
            "name": "Dart: Attach to Process",
            "type": "dart",
            "request": "attach",
            "observatoryUri": "http://127.0.0.1:33933/aAqCdEkfG4A=/"
        },