ACS-5449 Bump mockito-core from 4.9.0 to 5.4.0

[viepovsky]

First failure was caused by CamelComponentsTestclass , there were problems with bean initialization from test-messaging-context.xml. Above mentioned class along with CamelRoutesTest class uses this xml file. These classes had annotation @Category(NeverRunsTests.class), and after adding @Ignore to deactivate them, now tests pass. (I tried many ways of fixing test-messaging-context.xml file but didn't find any solution, only @Ignore makes it pass).

Edit: As @damianujma found out, that we cannot delete these tests, I backed to work to find solution for failing tests.
Finally I have found a solution for these camel tests, the error which caused problems was : No qualifying bean of type 'org.alfresco.repo.rawevents.TransactionAwareEventProducer' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {@org.springframework.beans.factory.annotation.Autowired(required=true)} and whatever I did it was not possible to mock certain classes (apart from TransactionAwareEventProducer class there were more exceptions for other mocked classes). Anyway after many tries, finally I inserted mocked beans on top of the application context xml file(test-messaging.xml) added type of argument and it does work now.
What caused the problem? Upgrading mockito-core from 4.9.0 to 4.10.0 and above causes this. I found one releted issue which I think is connected with this, as someone also had this problem, but they did not find solution. Anyway the solution is just putting mocked beans on the top of xml file before scanning spring components. Here is link to the issue: mockito/mockito#2779 (comment) , there is also mentioned that now when mocking and using xml, the type of argument is needed(it is also connected with the last failure with NodeLocatorServiceImplTest)

Second failure with access modifier, LockServicePoliciesImpl class was private, and after changing it to public there are no more IllegalAccessExceptions.

Third failure connected with RuleServiceImplUnitTest class, which tests RuleServiceImpl, this class has got private field SimpleCache<NodeRef, List<Rule>> nodeRulesCache;. And in RuleServiceImplUnitTest was field with raw interface without declaration just SimpleCache nodeRulesCache;, this caused problems in exception: java.lang.NullPointerException: Cannot invoke "org.alfresco.repo.cache.SimpleCache.remove(java.io.Serializable)" because "this.nodeRulesCache" is null.
After adding types to interface tests are passing.

The last failure was connected with NodeLocatorServiceImplTest class due to its bean initialization file test-nodeLocatorServiceImpl-context.xml, the problem was with recognizing proper overloaded method, I had to provide argument type (type=java.lang.Class), so the compiler could know which method to call.

[dsibilio]

See https://github.com/Alfresco/alfresco-community-repo/actions/runs/5609730718/job/15198015845#step:7:474.

Thanks @damianujma for noticing that the Camel tests were actually being run anyways successfully before the Mockito upgrade... so we actually kind of need to maintain them and fix issues that come with the Mockito upgrade rather than removing the tests. The name for the NeverRunsTests category was misleading.

[damianujma]

Even though the tests are "NeverRunsTest" annotated, these tests are run actually (e.g. https://github.com/Alfresco/alfresco-community-repo/actions/runs/5609730718/job/15198015845#step:7:474). I think we shouldn't remove them.

Still working on this