Fix ordering of Scheme toplevel attrs

[maxwellE]

Fix for incorrect ordering of Scheme attrs when
using wasCreatedForAppExtension value

[codecov-commenter]

Codecov Report

Merging #698 (972db0a) into main (e651344) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #698      +/-   ##
==========================================
+ Coverage   84.93%   84.96%   +0.03%     
==========================================
  Files         157      157              
  Lines        9127     9147      +20     
==========================================
+ Hits         7752     7772      +20     
  Misses       1375     1375              

Impacted Files	Coverage Δ
...urces/XcodeProj/Extensions/AEXML+XcodeFormat.swift	92.45% <ø> (ø)
...eProjTests/Extensions/AEXML+XcodeFormatTests.swift	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e651344...972db0a. Read the comment docs.

[kwridan]

Thanks @maxwellE

[kwridan]

minor: this test may be redundant, the order in which dictionary elements are specified to my knowledge is opaque to the underlying types, the dictionaries are equal between this test and test_Scheme_attributes_sorted_when_original_sorted, as such only one of those tests will suffice.

An interesting test could be the following (but may be overkill for this)

• Start with an unsorted raw XML (string) scheme
• Deserialize it (read it vis XCScheme)
• Serialize it back to XML
• Verify the correct sort order

[luispadron]

@maxwellE thanks for the PR. I've merged some of them and looks like that created a conflict here. Once that's resolved we can get this merged!