⚡️ Feature: Enable agents to be used as both edge/direct agents and as swarm node agents simultaneously

[EHLO1]

Feature Description

Enable a single instance of an Arcane Agent to act as an edge/direct agent for a Remote Environment, as a swarm node agent, or as BOTH simultaneously. Enable the main Arcane Instance to manage local swarm resources without needing its own local swarm node agent. Update Arcane Documentation to reflect new Arcane Agent workflows.

Creation of this feature also resolves the issue I created previously (#3092).

Problem It Solves

Currently, an Arcane Agent can either act as a an edge/direct for a Remote Environment OR it can act as a swarm node agent, but not both. The Arcane Agent binary is the same. How the agents are deployed is what locks them into one role or the other. This means if you want both, you are required to run 2 instances of the same Arcane Agent.

Proposed Solution

From a fresh install
Current Workflow

1. Deploy Main Arcane Instance
2. Create Environments
3. Deploy Edge/Direct Agents to the New Remote Environments
4. Initialize a Docker Swarm Cluster on the Main Arcane Instance
5. Deploy a Swarm Node Agent to the Arcane Main Instance's Local Node
6. Select Remote Environments, then Join Swarm Cluster
7. Return to the Main Arcane Environment
8. From the Main Arcane Environment, Deploy a Swarm Node Agent to Each Remote Environment

Proposed Workflow

1. Deploy Main Arcane Instance
2. Create Environments
3. Deploy Arcane Agents to the New Remote Environments
4. Initialize a Docker Swarm Cluster on the Main Arcane Instance
5. Select Remote Environments, then Join Swarm Cluster
   
   OR
   
   Allow "Easy Join" of Arcane Agent-Managed Nodes to the Arcane-Managed Docker Swarm Cluster

Resulting Changes to Agent Workflows

• Main Arcane Instance no longer needs its own local agent.
• Arcane Agents can be used for Remote Environments, Swarm Nodes, or both simultaneously.

Alternatives Considered

N/A - There really aren't any alternatives currently.

Additional Context

After Feature Request implementation, the Arcane Documentation should be updated to reflect new Arcane Agent workflows, such as Remote Environments, Docker Swarm, etc..

Would you be willing to work on this feature?

• Yes, I'd like to implement this feature
• I could help with parts of this feature
• No, I'm just suggesting the feature