fix ordering of snapshots

[ekohilas]

This PR releases a new version of ci-test that fixes a bug that essentially randomised the ordering of snapshots.

Now the ordering is fixed to be alphabetical on the values after the existence of if/changes.

e.g. Without this change, the ordering would be:

[
  {
    "changes": [
      "**/*.py"
    ],
    "jobs": [
      "job-rules-if-or-changes"
    ]
  },
  {
    "if": "$CI_PIPELINE_SOURCE == 'merge_request_event'",
    "jobs": [
      "job-rules-if-or-changes"
    ]
  },
  {
    "if": "$CI_PIPELINE_SOURCE == 'push'",
    "jobs": [
      "job-rules-if"
    ]
  },
  {
    "if": "$CI_PIPELINE_SOURCE == 'merge_request_event'",
    "changes": [
      "**/*.py"
    ],
    "jobs": [
      "job-rules-if-and-changes"
    ]
  },
  {
    "changes": [
      "**/*.json"
    ],
    "jobs": [
      "job-rules-changes"
    ]
  },
  {
    "jobs": [
      "job-rules-none"
    ]
  }
]

But now the ordering is:

[
  {
    "jobs": [
      "job-rules-none"
    ]
  },
  {
    "if": "$CI_PIPELINE_SOURCE == 'merge_request_event'",
    "jobs": [
      "job-rules-if-or-changes"
    ]
  },
  {
    "if": "$CI_PIPELINE_SOURCE == 'push'",
    "jobs": [
      "job-rules-if"
    ]
  },
  {
    "changes": [
      "**/*.json"
    ],
    "jobs": [
      "job-rules-changes"
    ]
  },
  {
    "changes": [
      "**/*.py"
    ],
    "jobs": [
      "job-rules-if-or-changes"
    ]
  },
  {
    "if": "$CI_PIPELINE_SOURCE == 'merge_request_event'",
    "changes": [
      "**/*.py"
    ],
    "jobs": [
      "job-rules-if-and-changes"
    ]
  }
]