Don't fail if the file flags of source and copied symlinks don't match.
Although there's no lchflags(), symlinks inherit file flags of their
parent directory(for history retention flags), so file flags may be set
on symlinks. chflags(1) on a symlink doesn't do anything nor does it
return an error code, so the new behavior is more consistent with
chflags(1)'s.
Symlinks don't inherit file flags on previous versions of DragonFly
or on FreeBSD, so this code has never had a chance to return ENOSYS.
Suggested-By: Matt