Make the module the sub-application

[MrWindlike]

What problem does this feature solve?
Currently, we use the $moduleId in the module to split the main application and the other modules, but it needs to evaluate the whole module template in the ModuleRenderer with the evalScope. This would lead to if some sub expressions evaluate wrong it would break the whole template's evaluation.

What does the proposed change?
Maybe we should make the module the sub-application, it could have its own StateManager and ApiService instance, then we don't need the $moduleId anymore and could evaluate the expression as the main application do.

[tanbowensg]

I think it could be a good idea. This could be the base of developing multiple page app by sunmao.

Module is vert similar to an application. The design $moduleId aims to isolate module's scope from application scope. If we use different sunmao instance, the problem will not exist anymore.
The problems are:

1. Allow different sunmao instances communicate will each other(expose state and events, just like what moduleRenderer do).
2. Fix the potential problems when multiple nested sunmao instances show in one screen, like dialog container problem.

We can keep the ModuleRenderer now ,and create a new ApplicationRenderer. We'd better not create a new spec. We can keep use the module spec.