Put STATE_LOCK_OWNER_9P under _USE_9P

Commit 56da7504cd09c67c41c59aa97f8fec8d2b3848a5 removed
STATE_LOCK_OWNER_9P from #ifdef _USE_9P.  This necessiated changes in
many switch statements and they don't look right for a reader! One of
the examples is listed below which imply that case STATE_LOCK_OWNER_9P
returns ht_nfs4_owner if _USE_9P is not defined. Of course, that
shouldn't happen, but if it happens, it would be an internal error.

        case STATE_LOCK_OWNER_9P:
                return ht_9p_owner;
        case STATE_OPEN_OWNER_NFSV4:
        case STATE_LOCK_OWNER_NFSV4:
        case STATE_CLIENTID_OWNER_NFSV4:
                return ht_nfs4_owner;

We could do something like below, but that looks ugly, so a better
option would be to go back to defining STATE_LOCK_OWNER_9P only under
_USE_9P.

case STATE_LOCK_OWNER_9P:
        do 9P specific stuff;
        /* This should never happen */
        LogFatal(COMPONENT_XXX, "This is an internal Ganesha error");

This patch puts STATE_LOCK_OWNER_9P under #ifdef _USE_9P back again!

Signed-off-by: Malahal Naineni <malahal@us.ibm.com>
Remove duplicate owner type comparisions.

Signed-off-by: Malahal Naineni <malahal@us.ibm.com>