Support separate installation paths for FXServer artifacts and server data

[CodexisPhantom]

Problem or Use Case

It would be interesting to decouple the FXServer installation path (artifacts) from the actual server data (data).
Currently, updating FXServer requires managing the artifacts within the same directory context or duplicating setups. Allowing a strict separation would enable developpers to maintain a single, centralized location for FXServer updates while having multiple server-data directories elsewhere.

Proposed Solution

Implement in the dxm new command something like : dxm new --only-data <path>

Alternative Solutions

No response

Additional Context

No response

[D4isDAVID]

What about something like dxm new --extend ..? Then the manifest file will contain something similar to:

[artifact]
extends = ".."

[CodexisPhantom]

Yep, and --extend would take a path to the artifact's parent folder, meaning no artifact would be downloaded to the new server. I tested changing the artifact in the dxm.toml file, and everything worked fine (though I guess I only checked if the server launches).

[D4isDAVID]

I'll keep this open until I properly implement --extend.