Cause: If the user specified a file or template source within a nested
directory, the role was using the whole path and not just the basename
for the name of the destination file.

Consequence: The role was trying to place files and templates in the
same directory structure on the destination, which is not supported
by systemd.

Fix: Ensure the basename of the given file or template is used to
construct the path to the destination.

Result: The role works even when the source files and templates are
in nested directories.

NOTE: If you were relying on the old broken code to make deeply nested
systemd and drop-in directories on the destination, and that somehow
was working, it will no longer be working.

Signed-off-by: Rich Megginson <rmeggins@redhat.com>