Add versioning to sources.json

[datenreisender]

For NCD-1128:

Effect of this change

Before we had an used a file sources.json which looked like this:

{
  "official": "https://developer.nordicsemi.com/.pc-tools/nrfconnect-apps/apps.json"
  "Test": "https://developer.nordicsemi.com/.pc-tools/nrfconnect-apps/test/apps.json"
}

This change introduces that instead a sources-versioned.json is used instead, which will look like this:

{
  "v1": [
    {
      "name": "official",
      "url": "https://developer.nordicsemi.com/.pc-tools/nrfconnect-apps/source.json"
    },
    {
      "name": "Test",
      "url": "https://developer.nordicsemi.com/.pc-tools/nrfconnect-apps/test/source.json"
    }
  ]
}

If an existing sources.json is found it is left untouched but the content is migrated to a new sources-versioned.json. If an sources-versioned.json is found, no migration is done. If neither a sources.json nor a sources-versioned.json is found, a new sources-versioned.json is created.

After the migration, only the contents of sources-versioned.json are used, any existing sources.json is ignored.

Motivation

With the move to Artifactory, I want to extend sources-versioned.json so that it can look like this:

{
  "v1": [
    {
      "name": "official",
      "url": "https://developer.nordicsemi.com/.pc-tools/nrfconnect-apps/source.json"
    },
    {
      "name": "Test",
      "url": "https://developer.nordicsemi.com/.pc-tools/nrfconnect-apps/test/source.json"
    }
  ]
  "v2": [
    {
      "name": "official",
      "url": "https://files.nordicsemi.com/ui/api/v1/download?isNativeBrowsing=false&repoKey=swtools&path=external/ncd/apps/official/source.json"
    },
    {
      "name": "Test",
      "url": "https://files.nordicsemi.com/ui/api/v1/download?isNativeBrowsing=false&repoKey=swtools&path=internal/ncd/apps/test/source.json"
    }
  ]
}

The idea is, that new versions of the launcher can use the new version v2 in this file, while old versions of the launcher can continue to use the old information.

It already would have been helpful and simplified the code if we had done a change like this when switching to using the new app meta data in #804. But now it is helpful too and if it already was helpful twice it might prove to be helpful again in the future.

Schema validation

Besides the migration to sources-versioned.json this change also adds schema validation to source.json. So the contents of all JSON files that are read of written there are also validated with zod.

[boundlesscalm]

Just to make sure I get the intention here, but why is this removed?

[datenreisender]

Almost two years after we switched from using apps.json to source.json files, I consider this code to be unneeded and wanted to clean up by removing it.

The only case when it would still be used, would be if someone would add a URL like https://developer.nordicsemi.com/.pc-tools/nrfconnect-apps/test/apps.json (instead of …/source.json) in the dialog to add a source.

[boundlesscalm]

Apart from a question I posted this looks nice and clean to me!