fix: ensure turbo stream names are generated based on decorated object

[markokajzer]

Description

closes #960 via suggested fix.

#928 introduced a subtle issue where turbo stream names are generated based on the decorated object, not the actual object as before.

[Alexander-Senko]

The goal is not just to fix Turbo's behavior in this particular case. We want GIDs to point to records every time they are passed between server and client sides. I hope #to_param is meant for that.

[Alexander-Senko]

Suggested change

	delegate :to_gid_param, to: :object
	delegate :to_gid_param, :to_sgid_param, to: :object

[markokajzer]

i totally missed this from your suggestion in the issue discussion... mb!

[markokajzer]

added delegation of to_sgid_param as well, sorry I missed that.

I'm not sure I fully understand your comment though as im not familiar with GlobalID all too much, so let me know if there are any other things we need to take care! 🙏

[Alexander-Senko]

The last thing is to figure out why SGIDs fail to match half of the time.

[markokajzer]

it seems like there's a timing related flake. A Signed Global ID seems to include an expiration timestamp in the ms range. Example:

{"_rails":{"data":"gid://dummy/Post/1","exp":"2026-03-14T14:20:07.394Z","pur":"default"}}

To get around that, I included ActiveSupport::Testing::TimeHelpers for this spec (since rails is loaded), and used freeze_time around it. In the run the expiration now ends in .000Z for both generations.

Let me know if that works 👍

[Alexander-Senko]

@markokajzer, thanks for your contribution, great job!

@seanlinsley, could we release a patch?