supply: use new mviews instead of table for status quo scenario

[nesnoj]

In DP v0.3 there will be only 1 table for RES and 1 table for conv. pp and 3 mviews for sq, nep2035 and ego100 scenarios for each of these tables (cf. openego/data_processing#109). In dingo, we must load the data from sq mview.
It'd be great to implement this prior to the next dingo run @gplssm.

[nesnoj]

I prefer to implement it once dp v0.3 will have been released since the current MVIEWs are in an unstable state (model_draft). If we would implement it now, we would have to update our defs again..
@wolfbunke, @ulfmueller: Is there a current, definite deadline (not the past one in the dp milestone) for the dp v0.3 release?

If

• there's no definite deadline and
• we do not highly depend on new datasets in eDisGo

I propose to postpone this issue to v0.1.4 and release v0.1.3 asap with the current tables.
Ok @gplssm ?

[nesnoj]

I adapted dingo to use the recent mviews from model_draft, in branch features/adapt-to-powerplant-mviews-dp-v0.3.0.
Tested successful on 1 MVGD.
The dingo exports can now be used for openego/eDisGo#21.

[ulfmueller]

concerning the deadline for the dp, I hand over to @IlkaCu

[IlkaCu]

I'll do my best to finish the dp release v0.3 before our project meeting next week.