Enable static imports in tests

[leventov]

As per https://lists.apache.org/thread.html/aed871e3a7d696c1e7a99085d0eab8b20b7c8efa76db3b75dc65f0cf@%3Cdev.druid.apache.org%3E

[kanibs]

Hey, Can I pick this?

[leventov]

@kanibs sure

[kanibs]

Hey @leventov, So I was going through all the attached resources in this issue- and to my understanding, I believe that we need to refactor the Unit Tests in such a way we have minimum statics and hence avoiding static imports and usages. Please correct me here if I have understood in a different way. If that is the case then fixing all the tests in a single PR would not be so easy. So can we break this PR in a more granular way to reduce the scope to a few Classes or maybe module wise, whichever is less?

[leventov]

The goal of this issue is just to fix hard&fast rule of prohibiting any static imports, which prohibits some fluent API patterns in test codebase. It can be literally a few lines of code tweaking checkstyle config (or whatever tool governs this for us, I don't remember)

[kanibs]

Hey @leventov, thanks for the suggestion/help. I have create the Pull request - #9764 for this.