fix(power-automate): fall back to classic Flow RP API when per-env PPAPI DNS fails (#284)

Older Default environments and some regional tenants never received
per-environment PPAPI DNS provisioning (*.environment.api.powerplatform.com).
When the derived hostname fails DNS resolution, all flow operations now
automatically fall back to the classic Flow RP endpoint. The fallback is
cached per-session so subsequent calls skip the failed probe.

Bumps plugin version to 2.1.0.

Fixes #269, #271, #274, #276, #278, #281, #282
Does NOT fix #280 (different issue: Button trigger listCallbackUrl)

Engine source: https://github.com/matow_microsoft/flow-agent/commit/d0d55f2

Co-authored-by: Matt Townsend <matow+microsoft@microsoft.com>

Author: radioblazer

plugins/power-automate/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "power-automate",
-  "version": "2.0.0",
+  "version": "2.1.0",
   "description": "Build, edit, run, and debug Power Automate cloud flows via the FlowAgent MCP server — connection lifecycle, surgical edits, copy across environments, run management, and validated expressions.",
   "author": {
     "name": "Microsoft",

plugins/power-automate/.plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "power-automate",
-  "version": "2.0.0",
+  "version": "2.1.0",
   "description": "Build, edit, run, and debug Power Automate cloud flows via the FlowAgent MCP server — connection lifecycle, surgical edits, copy across environments, run management, and validated expressions.",
   "author": {
     "name": "Microsoft",