project.json: seperate builds and packages

[Grashalmbeisser]

Seperate builds and packages in project.json so the package module does not interfere with custom builds.

Example:

{
    "default": {
        "application_name": "",
        "builds": {
            "app": {
                "command": "build",
                "kind": "npm",
                "source": "app"
            },
            "pyodide": {
                "clean": "rm -rf ./deploy/pyodide",
                "command": "python sources/viur-vi/vi/flare/tools/get-pyodide.py -t deploy/pyodide/",
                "kind": "exec"
            },
            "vi": {
                "clean": "rm -rf ./deploy/vi",
                "command": "python sources/viur-vi/vi/flare/tools/flare.py -s sources/viur-vi/vi -t deploy/legacy-vi",
                "kind": "package"
            }
        },
        "packages": {
          "admin": "4.1.5",
          "scriptor": "2.1.2",
          "core": "3.6.0b3"
        },
        "distribution_folder": "./deploy",
        "sources_folder": "./sources",
        "version": "$(year)-$(month)-$(day)-$(user)",
        "vue": {}
    },
    "format": "2.0.0",
    "live": {
        "application_name": ""
    }
}

[KadirBalku]

what is meant by different builds? this is already part of the cli.