UT: rm unrelevant, less logging in CI

[678098]

We have a stress test that calls close 10000 times, each close generates a log like this:

2025-11-25T23:57:53.1093092Z 23:57:52,218 (main) INFO BrokerSessionTest:186 Verify session event: BrokerSessionEvent [type: e_DISCONNECTED, error_desc: '']
2025-11-25T23:57:53.1093243Z 23:57:52,218 (main) INFO BrokerSession:505 Broker connection is stopping.
2025-11-25T23:57:53.1093402Z 23:57:52,218 (pool-13-thread-1) INFO BrokerSession:478 Stop callback: SUCCESS
2025-11-25T23:57:53.1093557Z 23:57:52,218 (pool-13-thread-1) INFO BrokerSession:1028 #### final stats ####
2025-11-25T23:57:53.1093626Z ::::: Events >>
2025-11-25T23:57:53.1093707Z          | messages| events| bytes
2025-11-25T23:57:53.1093782Z ---------+---------+-------+------
2025-11-25T23:57:53.1093861Z   PUT    |         |       |      
2025-11-25T23:57:53.1093938Z   CONTROL|         |       |      
2025-11-25T23:57:53.1094011Z   ACK    |         |       |      
2025-11-25T23:57:53.1094081Z   PUSH   |         |       |      
2025-11-25T23:57:53.1094150Z   CONFIRM|         |       |      
2025-11-25T23:57:53.1094155Z 
2025-11-25T23:57:53.1094225Z ::::: Queues >>
2025-11-25T23:57:53.1094309Z       |        In      |                 Out               
2025-11-25T23:57:53.1094421Z       | bytes| messages| bytes| messages| compression ratio
2025-11-25T23:57:53.1094518Z ------+------+---------+------+---------+------------------
2025-11-25T23:57:53.1094617Z queues|      |         |      |         |                  
2025-11-25T23:57:53.1094621Z 
2025-11-25T23:57:53.1094691Z ::::: Event Queue >>
2025-11-25T23:57:53.1094759Z   Queue | Queue Time
2025-11-25T23:57:53.1094831Z Abs. Max| Abs. Max
2025-11-25T23:57:53.1094895Z --------+---------
2025-11-25T23:57:53.1095020Z        1|  3.44 ms
2025-11-25T23:57:53.1095077Z 

This results in GH Actions being unusable with these logs. The solution is to suppress info level in log4j properties.

Also the PR removes outdated configs for broker and fixes broker binary launch.