fix(outputReferences): sorting of token without references

[vprothais]

Fixes #1350 (at least for the outputReferences case)

Issue Summary:
When using the outputReferences option, the tokens output is in reversed order compared to the input order. This is due to the end of the sortByReference method which defines that A comes first by default.

Considering the following input :

orange-10
orange-20
orange-100

We end up with :

--colors-orange-100
--colors-orange-20
--colors-orange-10

Description of changes:
At the end of the sortByReference method I introduced a return 0 in order to keep original order for token without reference. I introduced a test for the case bUsesRefs to still have A_COMES_FIRST since it was the previous return value for this case.

I also added a unit test for the two tokens without reference case and had to update some snapshot because of the new order. I checked all generated snapshot and the token using a ref is always declared after the referenced token.

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[aws-amplify-us-west-1]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-1362.d16eby4ekpss5y.amplifyapp.com

[jorenbroekema]

Aaaaaah so that's why! Good catch, thanks for contributing!