Cg util class

[ArsenHD]

Description

This MR allows moving all util methods that have previously been in the test class into a separate util class. The plugin will now generate utils in a separate class (org.utbot.runtime.utils.UtUtils).

If no util methods are required in the generated tests, then no util class will be generated. If the generated tests require util methods, but the tests do not use mocking, then a version of util class without mockito will be generated (when mocking is used, deepEquals util method is a bit different). Otherwise, when mocking is used, an util class with mockito usage will be produced.

For other components that use code generation the behavior may be different:

• TestCodeGenerationPipeline - Util class is generated, but only in tests where we use checkAllCombinations(). We check all combinations of generation settings with and without util class. But this shouldn't take much time, because we check all combinations only for a couple of classes.
• GenerateTestsAbstractCommand (CLI), GenerateTestsAndSarifReportFacade - we decided that these components should generate util class, but it is not implemented in this PR. For now they work as before, but in the future util class generation may be added.
• UtBotJavaApi, Contest - we decided that these components should not generate util class. They work as before, util methods are generated directly in the test class.

Type of Change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Automated Testing

Specify tests that help to verify the change automatically.

The following tests use function checkAllCombinations() that runs test generation with all configurations:
org.utbot.examples.codegen.CodegenExampleTest
org.utbot.examples.enums.ClassWithEnumTest#testOrdinal

Now all of these configurations also run with AND without a separate util class. This way the new feature is tested in the pipeline.

Manual Scenario

Note that util class can be overwritten if needed. This can be demonstrated and tested with the following actions:

1. We generate tests that need no utils --> no util class produced
2. Then we generate tests that do need utils (but with no mocks) --> util class without mockito produced
3. After that we generate tests that do need utils with mocks --> existing util class is overwritten with a new one that uses mockito.

Checklist:

• The change followed the style guidelines of the UTBot project
• Self-review of the code is passed
• The change contains enough commentaries, particularly in hard-to-understand areas
• New documentation is provided or existed one is altered
• No new warnings
• New tests have been added
• All tests pass locally with my changes