Rename Installation to Instance

Follows the portal: the noun is "instance" everywhere the app says it —
UI strings, CLI output, error details, docs and comments. The wire keys
(`instance_id`, `instance_token`) and the hub route this calls move with it.

An existing cloud.json is adopted rather than refused: without the key
alias the dataclass fails to parse, which the caller swallows and reads as
"never enrolled" instead of "reconnect".

`instance_key` on a node type becomes `target_key`. It means the outside
thing a node points at, which is a different sense of the word, and keeping
both would put two meanings of "instance" in one codebase.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015YrQnKV3bnQd4K342y8tKj

backend/fluksio/flow/nodes/mqtt.py

@@ -24,7 +24,7 @@ def _aiomqtt() -> Any:
     """The client library, which is a `fluksio[server]` extra.
 
     Imported per use rather than at module level, because the node type is
-    registered at boot and an installation that talks to no broker should not
+    registered at boot and an instance that talks to no broker should not
     have to carry the library to start.
     """
     try:
@@ -218,7 +218,7 @@ class MqttNode(Node):
         json_key: str | dict[str, str] = ""
 
     @classmethod
-    def instance_key(cls, params: dict[str, Any]) -> str | None:
+    def target_key(cls, params: dict[str, Any]) -> str | None:
         """The broker and topic, which is one physical thing.
 
         A publisher and a subscriber on the same topic get the same key on