BUG: make sure that the multi-index is lex-sorted before passing to _lexsort_indexer (GH8017)

BUG: sparse repr of multi-index frame with a FloatIndex as a level was incorrect

closes #8017 
but what has it to do with the level being float or not? The issue also occured with eg integer indices?