feat: Always generate enums with sorted members

[expobrain]

The code generator always renders the enum members in alphabetical order so that to minimise the changes in the generated code.

Tl;RL

Previously the enum members were collected as a dictionary in a random order and rendered as is, this was causing multiple run of the code generator to render the enum members in different order. If the generated code is then committed in a VCS it would create unnecessary changes because of the different order of the semantically same enum definition.

With this change the enum members are always rendered in alphabetical order so enums that are semantically the same will be rendered also the same in the code.

[dbanty]

I don't think the order was random, it should have been the order in which they were declared, so it should be consistent between runs.

However, this is better since even reordering the declaration in the schema shouldn't generate different code.

I wonder if we should do this with properties of objects as well 🤔

[codecov]

Codecov Report

Merging #728 (543db4d) into main (5f85ac5) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #728   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           49        49           
  Lines         1971      1971           
=========================================
  Hits          1971      1971           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[expobrain]

Probably yes, but in another PR