Better support for separate data paths

Feature Request

Is your feature request related to a problem? Please describe:

When using separate path for raftdb, tiup doesn't create the path if missing, also doesn't delete the path when cluster is destroyed.

Reproduce:

server_configs:
  tikv:
    raftstore.raftdb-path: "/data4/tabokie/tmp/raft"

deploy with error (tikv can't find the path):

Error: init config failed: 172.16.5.32:20187: executor.ssh.execute_failed: Failed to execute command over SSH for 'pingcap@172.16.5.32:22' {ssh_stderr: invalid configuration: entity not found
, ssh_stdout: , ssh_command: export LANG=C; PATH=$PATH:/usr/bin:/usr/sbin /data4/tabokie/tmp/tikv-20187/bin/tikv-server --config-check --config=/data4/tabokie/tmp/tikv-20187/conf/tikv.toml --pd=""}, cause: Process exited with status 1: check config failed

Describe the feature you'd like:

When config contains separate paths, take them into consideration on cluster setup/destroy.

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

Start by tracing tiup's cluster setup and destroy entry points for the tikv server_configs shown in the issue, focusing on how separate raftdb paths are handled. Verify the behavior with a missing /data4/tabokie/tmp/raft path: setup should account for it and destroy should clean it up.