Python settings should be parsed before the calling includeme

[cheungpat]

Currently py-skygear does the following in order before accepting requests from plugin transport:

• load python module
• call includeme
• call parse_all_settings

The desired order should be:

• load python module
• call parse_all_settings
• call includeme

In the desired order, the settings is available to module in includeme.

[rickmak]

Here is the example code that I comfirm the behaviour

at __init__.py

import os
import skygear
from skygear.settings import settings

settings.injectsettings.t = 'Code over ride'

skygear.config('injectsettings')

At injectsettings/__init__.py

from skygear.settings import add_parser, SettingsParser

s = SettingsParser('INJECT_SETTINGS')
s.add_setting('t', default='default t')
add_parser('injectsettings', s)

def includeme(s):
    print(s.injectsettings.t)

When I run INJECT_SETTINGS_T=portalvalue py-skygear injectsettings __init__.py

Expected result
Code over ride

Actual result (at 1.4.0)
portalvalue

Use-case

Developer want to override forgot password html template for beautiful design.