wrong logic in assertValidRoleAssignmentListResponse method
wrong logic in assertValidRoleAssignmentListResponse method

According to current logic, we always use the last of entities to
compare with ref. And, actually, we provide another method
assertRoleAssignmentInListResponse to judge whether the ref in the
list. So, the ref parameter could be removed.

Change-Id: I3f8786baa6964c0f17add2d669aa736732698ea7

takeshineshiro/keystone,vivekdhayaal/keystone,cernops/keystone,klmitch/keystone,ging/keystone,ilay09/keystone,roopali8/keystone,himanshu-setia/keystone,takeshineshiro/keystone,MaheshIBM/keystone,blueboxgroup/keystone,ajayaa/keystone,ilay09/keystone,dstanek/keystone,dims/keystone,ging/keystone,idjaw/keystone,rushiagr/keystone,promptworks/keystone,promptworks/keystone,nuxeh/keystone,UTSA-ICS/keystone-kerberos,vivekdhayaal/keystone,openstack/keystone,ilay09/keystone,cernops/keystone,jamielennox/keystone,maestro-hybrid-cloud/keystone,promptworks/keystone,nuxeh/keystone,jonnary/keystone,blueboxgroup/keystone,mahak/keystone,klmitch/keystone,openstack/keystone,nuxeh/keystone,idjaw/keystone,MaheshIBM/keystone,jamielennox/keystone,roopali8/keystone,mahak/keystone,rajalokan/keystone,rajalokan/keystone,jumpstarter-io/keystone,rajalokan/keystone,dstanek/keystone,jonnary/keystone,jumpstarter-io/keystone,himanshu-setia/keystone,vivekdhayaal/keystone,ajayaa/keystone,mahak/keystone,rushiagr/keystone,dims/keystone,rushiagr/keystone,maestro-hybrid-cloud/keystone,UTSA-ICS/keystone-kerberos,jumpstarter-io/keystone,openstack/keystone,dstanek/keystone