fix(autoware_pointcloud_preprocessor): fix potential double unlock in concatenate node

[vividf]

Description

This PR resolves a potential double unlock issue in the concatenate node. Previously, under certain conditions, the mutex could be unlocked twice, leading to undefined behavior and potential segmentation faults.

Related links

Note: This PR needs to rebase after #10074 is merged.

Parent Issue:

• Link

How was this PR tested?

• Tested with unit test.
• Tested with sample rosbag

Notes for reviewers

None.

Interface changes

None.

Effects on system behavior

None.

[github-actions]

Thank you for contributing to the Autoware project!

🚧 If your pull request is in progress, switch it to draft mode.

Please ensure:

• You've checked our contribution guidelines.
• Your PR follows our pull request guidelines.
• All required CI checks pass before marking the PR ready for review.

[codecov]

Codecov Report

Attention: Patch coverage is 60.00000% with 2 lines in your changes missing coverage. Please review.

Project coverage is 26.80%. Comparing base (59f2208) to head (c6ab579).
Report is 4 commits behind head on main.

Files with missing lines	Patch %	Lines
...oncatenate_data/concatenate_and_time_sync_node.cpp	33.33%	0 Missing and 2 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #10082      +/-   ##
==========================================
- Coverage   26.81%   26.80%   -0.01%     
==========================================
  Files        1414     1414              
  Lines      108279   108291      +12     
  Branches    41729    41730       +1     
==========================================
- Hits        29031    29026       -5     
- Misses      76367    76387      +20     
+ Partials     2881     2878       -3     

Flag	Coverage Δ		*Carryforward flag
differential	21.10% <60.00%> (?)
differential-cuda	19.38% <60.00%> (?)
total	26.80% <ø> (-0.01%)	⬇️	Carriedforward from 59f2208

*This pull request uses carry forward flags. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[knzo25]

@vividf
It seems there are several conflicts

[mojomex]

As remarked by @knzo25 offline some days ago, and as per the discussion @drwnz @vividf @manato and I just had,. it might be better to remove all locking completely as the callbacks within one node will always be in a mutually exclusive callback group by default, even when using a multithreaded executor.
This makes concat effectively single-threaded and thus no locking is needed. Performance hasn't be a problem even with our more data-heavy architectures.

[knzo25]

@mojomex
My comments though, require checking how threading, callback groups and timers work in ros.
In my experience, some timers (there are several, and some work at a lower level) had weird behaviors (different clocks were used ages ago, during some transitions, probably from ros1)