fix: do not use aliased attribute for order if model name is set

[bminer]

Pull Request Checklist

• [ ] Have you added new tests to prevent regressions?
• [x] If a documentation update is necessary, have you opened a PR to the documentation repository?
• [x] Did you update the typescript typings accordingly (if applicable)?
• [x] 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 Changes

Fixes #15422 by ensuring that the aliased attribute is not used when order is more than 2 elements (i.e. ["collection", "field", "ASC"])

Note that I have not created a test on this repo, but I do have a SSCCE: https://github.com/sequelize/sequelize-sscce/pull/243

List of Breaking Changes

[bminer]

Note: this is against the v6 branch. EDIT: ~~There will also need to be a fix for the main branch!~~

[WikiRik]

It seems that Oracle and MSSQL 2019 are currently broken in CI. I won't be able to look into it properly for another week at least (debugging from my phone is not smart to do). Oracle seems to be easy to fix, not sure what is wrong with MSSQL 2019

[bminer]

It seems that Oracle and MSSQL 2019 are currently broken in CI. I won't be able to look into it properly for another week at least (debugging from my phone is not smart to do). Oracle seems to be easy to fix, not sure what is wrong with MSSQL 2019

Be aware this is against branch v6, so the CI/CD might be different for this branch.

[bminer]

I do not think this problem exists in master branch (i.e. v7)

[bminer]

@WikiRik - Are you just waiting for me to implement a test for this? Is this fix acceptable otherwise?

[WikiRik]

Sorry for not responding before. It would be great if you could add a test

[bminer]

Listen, I will write the test, but I want to express some frustration here. I already did the SSCCE thingy, and this PR is for 2 lines of code...