fix(multi_object_tracker): input stream timimg functions

[technolojin]

Description

The input stream checked the object time interval inputs (object_latest_time and object_oldest_time) whether the latest time is later than the oldest time.
There was a report that the reversed timing settings (object_latest_time is older than object_oldest_time) was observed and the assertion stop the node, in the planning simulation environment.
#6820 (comment)

1. InputManager::getObjectTimeInterval
   Eliminated possibility to ouput the time interval settings (object_latest_time and object_oldest_time) in wrong order.

2. latest_object_time_ (renamed to latest_exported_object_time_)
   Initializing this value to now (time at the initialization) can cause the reversed times.
   This value will be initialized to a bit older than the initialization time.
   The value was renamed to avoid confusion.

3. InputStream::getObjectsOlderThan
   It checks the settings, but just warn (not assert) and return.

Tests performed

Regular test : TIER IV INTERNAL

Effects on system behavior

Not applicable.

Interface changes

Not applicable.

Pre-review checklist for the PR author

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

• I've confirmed the contribution guidelines.
• The PR follows the pull 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.

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.

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

[yukkysaito]

LGTM

[wep21]

@yukkysaito @technolojin still died

[multi_object_tracker_node-49] *** Aborted at 1717082878 (unix time) try "date -d @1717082878" if you are using GNU date ***
[multi_object_tracker_node-49] PC: @                0x0 (unknown)
[multi_object_tracker_node-49] *** SIGSEGV (@0x20) received by PID 461172 (TID 0x7df1e7c2f8c0) from PID 32; stack trace: ***
[multi_object_tracker_node-49]     @     0x7df1e548a206 (unknown)
[multi_object_tracker_node-49]     @     0x7df1e7a45320 (unknown)
[multi_object_tracker_node-49]     @     0x7df1e4932f0f TrackerObjectDebugger::process()
[multi_object_tracker_node-49]     @     0x7df1e48f8e08 TrackerDebugger::publishObjectsMarkers()
[multi_object_tracker_node-49]     @     0x7df1e48881e6 multi_object_tracker::MultiObjectTracker::publish()
[multi_object_tracker_node-49]     @     0x7df1e4887e5e multi_object_tracker::MultiObjectTracker::checkAndPublish()
[multi_object_tracker_node-49]     @     0x7df1e48875cc multi_object_tracker::MultiObjectTracker::onTimer()
[multi_object_tracker_node-49]     @     0x7df1e48cf76d std::__invoke_impl<>()
[multi_object_tracker_node-49]     @     0x7df1e48c98e9 std::__invoke<>()
[multi_object_tracker_node-49]     @     0x7df1e48c449b _ZNSt5_BindIFMN20multi_object_tracker18MultiObjectTrackerEFvvEPS1_EE6__callIvJEJLm0EEEET_OSt5tupleIJDpT0_EESt12_Index_tupleIJXspT1_EEE
[multi_object_tracker_node-49]     @     0x7df1e48bdab5 std::_Bind<>::operator()<>()
[multi_object_tracker_node-49]     @     0x7df1e48edabc rclcpp::GenericTimer<>::execute_callback_delegate<>()
[multi_object_tracker_node-49]     @     0x7df1e48ea877 rclcpp::GenericTimer<>::execute_callback()
[multi_object_tracker_node-49]     @     0x7df1e8307a51 rclcpp::Executor::execute_any_executable()
[multi_object_tracker_node-49]     @     0x7df1e8319234 rclcpp::executors::SingleThreadedExecutor::spin()
[multi_object_tracker_node-49]     @     0x65224930e45c main
[multi_object_tracker_node-49]     @     0x7df1e7a2a1ca (unknown)
[multi_object_tracker_node-49]     @     0x7df1e7a2a28b __libc_start_main
[multi_object_tracker_node-49]     @     0x65224930dac5 _start

[yukkysaito]

@wep21 Thanks for the report.

@technolojin , may I ask you to analyze the bug?

[technolojin]

@wep21 Thank you for your report.
The message indicates seems to be an another issue.
However I couldn't reproduce this issue from my environment.

Based on the error message, I created a trial of the bug fix. #7347
Can you test this modification?