Clarify publish behavior for shared_ptr and unique_ptr

[Yuchen966]

Description

Updates some explanation of intra-process communication demo document to reflect the actual current behavior with respect to function publish():

• shared_ptr messages: Cannot be published (removed incorrect zero-copy claims)
• unique_ptr messages: Zero-copy transfer achieved for the last subscriber
• raw messages: Both msg and std::move(msg) result in copying

Key changes:

• Add notes about current behaviour
• Correct the explanation that all subcribers except for the last one will receive copies of published messages.

Fixes issue

Did you use Generative AI?

No

Additional Information

[alsora]

these statements are not really correct.
you can't infer this from publisher alone, but only from the combination of publisher and subscriber.

[fujitatomoya]

extra '~'?

Suggested change

	Understanding publish() behavior with different message types
	~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
	Understanding publish() behavior with different message types
	~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[fujitatomoya]

@Mergifyio rebase

[mergify]

rebase

✅ Branch has been successfully rebased