fix: aggregate with parent ref in relationship filter and sorting on relationship field

[ahey]

Contributor checklist

Leave anything that you believe does not apply unchecked.

• I accept the AI Policy, or AI was not used in the creation of this PR.
• Bug fixes include regression tests
• Chores
• Documentation changes
• Features include unit/acceptance tests
• Refactoring
• Update dependencies

[zachdaniel]

@ahey is this a consequence from your other change? Extracting parent refs is not something that are on the table nor should we have to do it. Is there a specific bug you're looking to fix?

[ahey]

@zachdaniel this is unrelated to the other change. Here is the test that reproduces the issue: ash-project/ash_postgres#658

[zachdaniel]

Got it. I'll have to look into this further this week or this weekend because I don't think we can extract refs like this in general, there are too many edge cases. We would instead likely need to do something when adding the aggregates themselves where the filter ends up being fully hydrated to track what parent attributes are referenced to ensure they are selected for example.

[ahey]

Thanks @zachdaniel for your help and the update.

[zachdaniel]

Actually, I think this covers enough and does actually solve the issue, there might just be some additional work downstream to expand certain kinds of references. This also helped me fix another issue also. Thanks!

[ahey]

You're most welcome, and thank you for your help on this! All tests are passing on my ash projects 😄