fix(sensor_calibration_manager): fixed sensor calibration manager related issues

[knzo25]

Description

Upon the release of the new api, two problems were encountered:

• When closing the sensor calibration tools or sending sigint/sigkill to the terminal, sometimes zombie processes remained
• When the sensor calibration manager started and there were no tfs available, the state machine got stuck and never became able to calibrate

  Related links

Tickets:

• TIER IV INTERNAL LINK
• TIER IV INTERNAL LINK

Tests performed

After the Launcher configuration widget, the sensor calibration manager executes the respective launchers. In this condition, even if we close the sensor calibration manager via widget or console, no zombies remain

(can be checked with ps -aux | grep ros) or similar

Previously, if we ran the sensor calibration manager until after the launchers were executed with no autoware nor rosbag (which publishes the /tf_static), even if we started autoware or the rosbag afterwards, the calibration tool never became able to calibrate due to the design of the internal state machine. With this PR, is should be fixed

Notes for reviewers

Pre-review checklist for the PR author

The PR author must check the checkboxes below when creating the PR.

• [x] I've confirmed the contribution guidelines.
• pull request guidelinesull request guidelines].

In-review checklist for the PR reviewers

The PR reviewers must check the checkboxes below before approval.

• [ ] The PR follows the pull request guidelines.
• [ ] The PR has been properly tested.
• [ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author

The PR author must check the checkboxes below before merging.

• [ ] There are no open discussions or they are tracked via tickets.
• [ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

[knzo25]

@vividf Did you confirm that the changes fixes the issues on your environment? (the two issues this PR addresses)

[vividf]

@knzo25 Yes, the button will be enabled even /tf comes later, also all of the processes are killed.

[knzo25]

@vividf Thanks for the check !