OAK-12300 : Remove ServiceListener after awaitServiceEvent completes

[rishabhdaim]

No description provided.

[github-actions]

Commit-Check ❌

Commit rejected by Commit-Check.                                  
                                                                  
  (c).-.(c)    (c).-.(c)    (c).-.(c)    (c).-.(c)    (c).-.(c)  
   / ._. \      / ._. \      / ._. \      / ._. \      / ._. \   
 __\( C )/__  __\( H )/__  __\( E )/__  __\( C )/__  __\( K )/__ 
(_.-/'-'\-._)(_.-/'-'\-._)(_.-/'-'\-._)(_.-/'-'\-._)(_.-/'-'\-._)
   || E ||      || R ||      || R ||      || O ||      || R ||   
 _.' '-' '._  _.' '-' '._  _.' '-' '._  _.' '-' '._  _.' '-' '._ 
(.-./`-´\.-.)(.-./`-´\.-.)(.-./`-´\.-.)(.-./`-´\.-.)(.-./`-´\.-.)
 `-´     `-´  `-´     `-´  `-´     `-´  `-´     `-´  `-´     `-´ 
                                                                  
Commit rejected.                                                  
                                                                  
Type message check failed ==> OAK-XXXXX: Remove ServiceListener after awaitServiceEvent completes

The EventServiceListener was never removed from the BundleContext after
awaitServiceEvent completed (either successfully or via timeout). This caused:

1. Resource leaks - listeners accumulated across test runs
2. Test interference - listeners from previous tests continued receiving events
3. Intermittent test failures - unrelated service events could be captured,
   causing timeout errors when waiting for specific service events

Fix: Add try-finally block to ensure bundleContext.removeServiceListener()
is always called after the await completes, preventing listener accumulation
and cross-test event interference.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> 
The commit message should follow Conventional Commits. See https://www.conventionalcommits.org
Suggest: Commit message does not match the required pattern

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud