verdi import --in-place crashes when export file is on different file system

[ltalirz]

Describe the bug

verdi import --in-place assumes that the temporary directory and the working directory are on the same file system.
If that is not the case, one can run into errors like these:

   Traceback (most recent call last):
      File "/home/ubuntu/.virtualenvs/aiida/bin/verdi", line 12, in <module>
        sys.exit(verdi())
      File "/home/ubuntu/.virtualenvs/aiida/lib/python3.6/site-packages/click/core.py", line 764, in __call__
        return self.main(*args, **kwargs)
      File "/home/ubuntu/.virtualenvs/aiida/lib/python3.6/site-packages/click/core.py", line 717, in main
        rv = self.invoke(ctx)
      File "/home/ubuntu/.virtualenvs/aiida/lib/python3.6/site-packages/click/core.py", line 1137, in invoke
        return _process_result(sub_ctx.command.invoke(sub_ctx))
      File "/home/ubuntu/.virtualenvs/aiida/lib/python3.6/site-packages/click/core.py", line 1137, in invoke
        return _process_result(sub_ctx.command.invoke(sub_ctx))
      File "/home/ubuntu/.virtualenvs/aiida/lib/python3.6/site-packages/click/core.py", line 956, in invoke
        return ctx.invoke(self.callback, **ctx.params)
      File "/home/ubuntu/.virtualenvs/aiida/lib/python3.6/site-packages/click/core.py", line 555, in invoke
        return callback(*args, **kwargs)
      File "/home/ubuntu/aiida-core/aiida/cmdline/commands/cmd_export.py", line 235, in migrate
        os.rename(output_file, input_file)
    OSError: [Errno 18] Invalid cross-device link: '/tmp/tmpkoqd1ucq/archive.aiida' -> '/home/ubuntu/aiida_profiles/home/ubuntu/.aiida/repository/sssp/archives/SSSP.1_5.aiida'

os.rename should be replaced by shutil.move

Steps to reproduce

1. Place an AiiDA export file on a file system that is not the root volume (the one hosting temporary files)
2. Try importing that file via verdi import --in-place

Your environment

Current aiida-core develop branch.

Additional context

One can use the TMPDIR environment variable to work around this issue by setting it e.g. to the current working directory.