fix(postgres): add custom order direction to subQuery ordering with minified alias

[evanrittenhouse]

Pull Request Checklist

• Have you added new tests to prevent regressions?
• If a documentation update is necessary, have you opened a PR to the documentation repository?
• Did you update the typescript typings accordingly (if applicable)?
• Does the description below contain a link to an existing issue (Closes #[issue]) or a description of the issue you are solving?
• Does the name of your PR follow our conventions?

Description Of Change

Fix for new issue raised at #14723.

Essentially, we weren't pushing the order direction when pushing the alias for the sub-query field. This PR adds logic to do so, as well as tests for ascending/descending subquery ordering with aliases.

[WikiRik]

Could you add the unit test that was in the original comment as well?

[evanrittenhouse]

@WikiRik Sorry, what unit test do you mean? I believe the original issue's case is covered in the orderByDescSubquery test found here, unless I'm misunderstanding the issue they're having.

[WikiRik]

I think I was just confused. This integration test indeed covers this just fine

[evanrittenhouse]

Sweet, once the checks pass I'll merge and notify Ashby on the issue thread.

[evanrittenhouse]

@WikiRik can you please re-approve? Rebased on top of main so I can merge if (fingers crossed when) the checks pass.

[WikiRik]

For next time; you can just merge main in and push the new commit. If there are no conflicts you need to resolve, it won't discard my review.
And we squash all commits upon merging so that's not an issue.

Also; can you backport this to v6 as well?

[ephys]

OK if I trigger a v7 release that includes this change?

[WikiRik]

Go ahead! Could be the final pre-DataTypes release

[github-actions]

🎉 This PR is included in version 7.0.0-alpha.18 🎉

The release is available on:

• npm package (@release-v7 dist-tag)
• GitHub release

Your semantic-release bot 📦🚀