Add static assert for removed subscription callback signatures

[mini-1235]

Description

• Add static assert for removed subscription callback signatures

Fixes #2972

Is this user-facing behavior change?

Yes

Did you use Generative AI?

No

Additional Information

When working on this PR, I noticed that #1713 only deprecates MessageT. However, looking at the comment here:

rclcpp/rclcpp/include/rclcpp/any_subscription_callback.hpp

Lines 140 to 154 in eb49444

	// Deprecated signatures:
	using SharedPtrCallback =
	std::function<void (std::shared_ptr<SubscribedType>)>;
	using SharedPtrROSMessageCallback =
	std::function<void (std::shared_ptr<ROSMessageType>)>;
	using SharedPtrWithInfoCallback =
	std::function<void (std::shared_ptr<SubscribedType>, const rclcpp::MessageInfo &)>;
	using SharedPtrWithInfoROSMessageCallback =
	std::function<void (
	std::shared_ptr<ROSMessageType>,
	const rclcpp::MessageInfo &)>;
	using SharedPtrSerializedMessageCallback =
	std::function<void (std::shared_ptr<rclcpp::SerializedMessage>)>;
	using SharedPtrSerializedMessageWithInfoCallback =
	std::function<void (std::shared_ptr<rclcpp::SerializedMessage>, const rclcpp::MessageInfo &)>;

it looks like the type_adaptation/serialized message are not yet deprecated, how should we proceed?

In the meantime, I have also updated the tests for type_adaptation/serialized to use std::shared_ptr<const>

[mini-1235]

I have pulled and built the ROS2 repos from https://raw.githubusercontent.com/ros2/ros2/rolling/ros2.repos (Please let me know if there are any other repos I should include)

Removing std::shared_ptr<MessageT> would have an impact on:

• robot_state_publisher: Update subscription callback signatures ros/robot_state_publisher#241
• real_time_support: Update subscription callback signatures realtime_support#135 (example)
• message filter: Update subscription callback signatures message_filters#222 (test only)
• demos: Update subscription callback signatures demos#754

Removing/Deprecating std::shared_ptr<TypeAdapter/Serialize Message> would affect:

• demos: Update subscription callback signatures demos#754
• ros2 tracing: Update subscription callback signatures ros2_tracing#217 (test only)
• rosbag2 (examples and test): Update subscription callback signatures rosbag2#2225
• system test: Update subscription callback signatures system_tests#575

[fujitatomoya]

@mini-1235 thanks for fixing up all the related packages and repositories.

changing signatures are totally fine things to do including this PR, but i want to discuss with you on either we should enforcement or deprecation here for the next release.

[fujitatomoya]

It is true that those signatures have been deprecated for a long time as comment states, but my concern is that can we really enforce this all the sudden? i understand this is right thing to do, but this can possibly break the user space without any notification.

IMO, Deprecation Period should still be given for user space for next release, and then we can enforce the invalid signature assertion?

@mini-1235 @mjcarroll @ahcorde what do you think?

[mini-1235]

I think there are two points to discuss here:

1. std::shared_ptr<MessageT>: this was deprecated back in August 2021, but the deprecation warning was accidentally removed in February 2024. It looks like the majority of the ROS 2 core repositories are fine, but I am not entirely sure about other packages. For example, Nav2 still uses std::shared_ptr<MessageT> a lot: mini-1235/navigation2@9a6aca5

2. std::shared_ptr<TypeAdapter/Serialize Message>: this signature was actually never deprecated, so I think it should be deprecated instead of removed

In my current PR, I removed all forms of std::shared_ptr<> mainly for testing purposes. I am open to any suggestions on how this should be handled :)