feat: preserve keys order when using getters and virtual fields

[evsar3]

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

On a model that has getters and virtual fields, when serialized to JSON these fields are placed on top of the object. This PR implements sorting for the objects keys following the order they were declared on the model schema.

I have made this PR previously (#16169), but I was closed due to the PR not following some contribution guidelines. I have tried by best to make this match our guidelines and hope this get merged.

Thank you.

Happy New Year!

[WikiRik]

Thanks for working on this more. Could you add some tests?

[evsar3]

Have added the tests that verifies if the result of keys of<modelInstance>.get() is the same as the order of keys of Model.modelDefinition.rawAttributes

Not sure if this is the right location for placing this test, let me know if I should move it into another file.

[ephys]

I'm not really a fan of this approach as it's going to be pretty expensive just for what is pretty much a cosmetic change

If we want to do this, we should iterate modelDefinition.attributes.keys first, assign any value that exists, then iterate dataValues and add any value that wasn't added yet. This would respect the definition order without needing to sort after the fact