Load mysql dump to speed up migrations during quickstart

[kdmccormick]

Context

TBD

Acceptance

TBD

[ARMBouhali]

So instead of long init tasks passing through django management commands, one can generate sql files out of these and offer to apply them as conditional init tasks.

I like the idea and I am interested in seeing how deep we can go implementing it .

[regisb]

For the record, this is a question that was raised before: overhangio/tutor#238
This feature is more feasible now that we have a more extensive plugin API. Still, I think that loading a dump instead of running migrations would cause more issues than it would resolve. I'd love to be proven wrong, though.

[kdmccormick]

I think this issue has a lot of potential for increasing launch speed, but also comes with maintenance challenges. Specifically: the sql files would need to be updated regularly as init tasks are changed, both in Tutor and in the underlying upstream management commands. Django upgrades can affect the sql dump, too.

I would be supportive if someone wanted to implement this a plugin and propose a maintenance plan for the plugin, probably including automatic regeneration of the dumps using vanilla Tutor. I think vanilla Tutor should continue to use management commands, as they are more human-readable than SQL, and they largely come pre-written for us from upstream.

[kdmccormick]

In the grand scheme of things, Tutor launch time is pretty darn good, so I'm not keen on spending time on this and potentially introducing bugs. I'm going to close this, and we can come back to it if we find that Tutor launch isn't fast enough.