Add preview stability support for the ability to copy a resource and its children to a new resource under a different name.

This can be both useful on its own as a convenience but can also function as a primitive allowing aggregate operation like a 'rename', i.e. done as a copy+remove.

A optional requirement / possible further enhancement is to allow specifying the target parent resource, e.g. to copy a subsystem from one profile to another in a domain-wide configuration. That could also then act as a primitive for a 'move' operation.

We need to investigate whether this is best done as a new 'global 'operation (https://docs.wildfly.org/33/Admin_Guide.html#Global_operations) or via a CLI high-level command.

If it's a global operation it's not truly global, as it only applies to persistent resources, not runtime-only ones. This is somewhat analogous to 'add' and 'remove' but with a critical difference – for 'add' and 'remove' every resource must implement a handler, while for a, for example, 'copy-resource' we need a single handler, but only registered with persistent resources.

If it's a global operation the name is important, as whatever name is used must be unlikely to conflict with any existing operation name. (That's why I used 'copy-resource' and not just 'copy' in my example above.)

A reasonable restriction, at least initially, is this op would fail if run on a non-admin-only process.

This should start at Preview or Experimental stability in order to get bake before promotion to community. Which we choose should depend on how confident we are in the API and general behavior.