Configurable seeding

[xmichaelx]

Current seeding mechanism is hardcoded could we have the same logic but imported from a configuration file? This would ease the trouble for devopses when deploying new instances of IS by allowing for having some parts preconfigured. Also instead of constants we should opt for options

Sth like the following:

{
    "Roles": [
        {
            "Name" : "",
            "Claims" : [],
            "IsAdminRole" : true // this is for knowing which role name to configure as the main one
        }
    ],
    "Resources": [
        {
            "Name" : "api1",
            "Scopes" : [
                { 
                    "Name": "api1",
                    "Claims" : [

                    ]
                }
            ]
        }
    ],
    "Users" : [
        {
            "Username" : "",
            "Email" : "",
            "Password" : ""
        }

    ], 
    "Clients" : [
        {
            "ClientId" : "",
        }

    ]
}

[skoruba]

Done in the master branch