Issue #7877: Fix for ImprtOrderCheck(6)

[yajna-pandith]

#7877: Fix for ImprtOrderCheck(6)

[wltan]

Please read the main issue #7797 again and follow the steps in there. It is not as simple as deleting code that causes surviving mutations.

If you want to remove code, you have to justify why that code is not used and can be safely removed without affecting functionality.

Otherwise, the code is actually being used, but our unit tests are not comprehensive enough to cover programming mistakes (mutations) in that section. In that case, you need to design new UTs that will (correctly) fail when the source code is mutated.

Whatever work you do needs to be accompanied by the relevant pitest and regression reports, as stated in the main issue.

[rnveach]

Waiting on things @wltan mentioned. We need proof that all we can do is remove the code and why.

[romani]

@yajna-pandith , ping, please provide prove that removal of code does not make any regression.
please generate diff report by checksgtyle-tester on all projects in properties file, please share report.

[romani]

we lost connection to @yajna-pandith , PR is closed as incomplete.