Added checks for "from" field in pgSelect dedup function

[kzlar]

Description

https://discord.com/channels/489127045289476126/498852330754801666/1312193983308365865
I think I found a potential edge case, wondering your thoughts on it. I have two plans implemented in makeExtendedScemaPlugin, both are implemented manually with calling pgSelect with a custom from function. I'm calling both of them in a query and I think they're getting deduplicated, even though from implementation is different.

Performance impact

unknown. Theoretically it would deduplicate less than before, but I think that any such deduplications would have been erroneous.

Security impact

unknown, but don't expect it to change anything.

Checklist

• My code matches the project's code style and yarn lint:fix passes.
• I've added tests for the new feature, and yarn test passes.
• I have detailed the new feature in the relevant documentation.
• I have added this feature to 'Pending' in the RELEASE_NOTES.md file (if one exists).
• If this is a breaking change I've explained why.

[changeset-bot]

🦋 Changeset detected

Latest commit: cba6ee0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 7 packages

Name	Type
@dataplan/pg	Patch
ruru-components	Patch
graphile-utils	Patch
graphile-build-pg	Patch
pgl	Patch
postgraphile	Patch
graphile	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR