Cleanup refcounting in FSAL

fsal_module refcounting is now atomic instead of under lock.

fsal_put is now an inline function.

Make sure fsal_put is called in correct places.

fsal_export no longer has a refcount or get/put methofs. fsal_exports
are always attached to an exportlist_t/gsh_export and this the
refcounting on gsh_export is sufficient.

fsal_obj_handle no longer has a refcount or get/put methods.
fsal_obj_handles are either attached to a cache inode, and will be
managed by the cache inode refcount, or are tempory objects that are
immediately released.

Since the return code for release was pretty much never checked for
any of these objects, and most release methods can't actually fail,
all release methods are now void return.

Several fsal_obj_handle methods attempted to deal with making sure
the file was closed. None of the close routines actually fails to
close the file (there may be an error, but for example, the
system call close never fails to release the file descriptor). The
error checking in these cases has been cleaned up.

fsal_obj_handle methods that checked if the file was closed have
been modified to close the file (if the return code from release
wasn't going to be checked, and the caller wasn't going to continue
to reference the fsal_obj_handle, no one would ever close it otherwise).

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Remove FS_JUNCTION file type

This was never used, and improperly handled.

If in the future we actually need such a type, we can re-introduce it
with proper handling in all places.

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>