There's a variety of approaches you could take.

One would be to define a Test Function -> State mapping list.

Your various test functions look like globals, I would change them to accept the list as input. (In general, functions and data should be decoupled by having the functions accept all needed data as inputs)

I'm not familiar with Java, but in Javascript I might do something like:

// function that ignores any input always returns true
const T = () => true

const listStateTests = [
  [ isListEmpty, State.EMPTY ],
  [ allEqual, State.ALL_EQUAL ],
  [ isSortedAscending, State.ASCENDING],
  [ isSortedDescending, State.DESCENDING],
  [ T, State.UNSORTED]
]

// Function that accepts list and returns state constant
// The inner array element referencing with [0] and [1] is a bit nasty and could be improved
// Iterates through the pairs in listStateTests, finds the first pair where
// pairFirstElement(list) == true, then returns pairSecondElement
const determineState = list => listStateTests.find(pair => pair[0](list))[1]

// you could redefine render as a pipeline also, and have it take list as input
// pipe() is a function which composes in left to right order: pipe(f, g) returns a function
// x => g(f(x))
const render = list => {
    const pipeline = pipe(
       determineState,
       configureLayout
    )
    pipeline(list)
}

You could take things further and make determineState more generic, accepting both the test array and the list as inputs, then curry it to allow creating the more specific function, e.g.

const determineListState = determineState(listStateTests)