allow ordering static dropdowns

[xavdid]

fixes zapier/zapier-platform-cli#125 in a less-hacky way.

Side note, this was a bear to test. Had to hack apart the CLI and server to forego any form of validation so I could figure out what structure(s) worked before writing the schema for it.

[eliangcs]

This seems to be the right way to support ordered static field choices. Two questions:

1. Can we add a test for it?
2. Does the backend already support this new schema?

[xavdid]

Schema is tested via the examples and antiExamples arrays in the schema itself. The test iterates through all the schemas and makes sure that all examples validate and none of the antiExamples do (link). So each of the new ones has some simple tests built in!

Backend does support it! Once the app builds, it ships that json straight to the backend. It does server validation and then stores it. From there, it gets processed by formatic (which is the software that powers the editor). So we have to match the format it's expecting, but that's all we need.

My app:

local editor:

Test result (just returns input):

I couldn't test against prod since the server validation uses the published version (I think), but i could disable that locally and the editor handled the json correctly.

[eliangcs]

Thanks for the clarification! I think you need to rebuild doc and schema then it's good to merge:

npm run docs
npm run export

[xavdid]

yep! i was going to let the release take care of that so the docs aren't in master before the code is deployed (which would be confusing)

[eliangcs]

@xavdid sounds good!