Be sure a user cannot server import crafty dir

What does this MR do and why?

Currently a Crafty user could create a malicious attack if they were able to find out the absolute path of the Crafty directory a user could import an entire root directory as a server and cause a copy loop until the system drive is completely full and rendered useless.

This MR will fix this issue and make sure Crafty does not exist inside whatever directory is being imported as a server.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• Have you checked this doesn't interfere/conflict/duplicate someone elses work?
• Have you fully tested your changes?
• Have you resolved any lint issues?
• Have you assigned a reviewer?
• Have you applied correct labels?