LPS-44476 SF
LPS-44476 Adopt a single, consistent style across all test classes

* Avoid magic numbers and magic strings
* Prefer `RandomTestUtil` over arbitrary literal constants
* Match `setUp` method names to the class being prepared
* `BasicRegistryImpl` renders a mock Registry unnecessary

https://issues.liferay.com/browse/LPS-44476
LPS-44476 anonymous classes can stay anonymous
LPS-44476 Can we add these to the test method name somehow. I find some of these messages helpful, but some are obvious / repetitive and inconsistent
LPS-44476 SF
LPS-44476 These can be private
LPS-44476 Says the same thing
LPS-44476 Says the same thing
LPS-44476 Use inheritance
LPS-44476 SF
LPS-44476 Sometimes, to many methods causes confusion too
LPS-44476 So this is a good example. The method name is actually not true. To be very true, we would have to say that we also assert that file entry tuples and mb messages are empty. But that gets too long. So in cases where specific method names are NOT accurate, go for a generic name to force the developer to read the code to find what the method actually does.
LPS-44476 Match previous commit even though this method name was accurate
LPS-44476 Simplify. In SearchResultUtilJournalArticleTest, I kept the extra method because it is many lines of code. In SearchResultUtilMBMessageTest I removed the method for simplicity. They are all one liners.
LPS-44476 Simplify
LPS-44476 Simplify
LPS-44476 SF
LPS-44476 SF
LPS-44476 Even though you had it sorted alphabetically by searchResult.*. It requires knowledge of the implementation of assertEmptyFileEntryTuples and assertEmptyMBMessages. Let's sort the asserts where we actually call searchResult.get* and then sort the ones where we delegate the method name
LPS-44476 Simplify