Support composite primary keys

[shahryarjb]

Code of Conduct

• I agree to follow this project's Code of Conduct

AI Policy

• I agree to follow this project's AI Policy, or I agree that AI was not used while creating this issue.

Is your feature request related to a problem? Please describe.

Sometimes a project needs to keep history of a resource changes which just has for example 2 belongs_to which are primary_key?: true without any other attributes, But i think it is not supported for now
based on

ash_paper_trail/lib/resource/transformers/create_version_resource.ex

Line 138 in 409bfdf

Resources with composite primary keys are not currently supported. Got keys #{inspect(keys)}

Describe the solution you'd like

I would be very good to add it in ash_paper_trail.
For example we can have all history of team member which want to join (add) or left the team (destroy)

Describe alternatives you've considered

No response

Additional context

Thank you in advance

Discord link:
https://discord.com/channels/711271361523351632/1253438465543245844/1429155896218615999

[zachdaniel]

The specific thing here is not necessarily relationships with primary_key?: true, it's composite primary keys that need to be supported.

[zachdaniel]

This likely won't be too hard for whoever wants to pick it up. There will be a more complex has_one relationship set up to the version source, which will use multiple attributes instead of just the one with a belongs_to.