Refactoring wrt-setting

Refactoring wrt-setting

[Issue#]    N/A
[Problem]   Current wrt-setting has too many uncleaned source.
[Cause]     wrt-setting hasn't managed quite long-term since
            web application details menu is disabled.
            As new UX concept is added, it's time to refactoring.
[Solution]  Refactoring
            - Refactoring "ug.cpp"
              ug.cpp is start point of menu and interface between ug manager and menu implement.
              Current tizen platform requires that all ug should implement ug_module_ops
              for interface and return layout(Evas_object*) to connect UI by elementary base.

              Description ug.cpp
              1. Interface between ug manager(callee process) and mainview instance.
              2. Receives package information by service_h.
              3. Create mainview instance.
              4. Get layout for passing to ug manager from mainvuew instance.

              Refactoring details
              - Replace calloc and free to std::unique_ptr which is used managed mainview instance.

            - Refactoring "MainView"
              Description "MainView"
              1. Create base UI.(layout, bg, naviframe)
              2. Create and manage ExceptionView instacne.

              Refactoring details
              - Replace DPL::ScropedPtr to std::unique_ptr which is used to
                manage ExceptionView instance.
              - Separate UI create parts to each method
[SCMRequest] N/A

Change-Id: Id7e9734cc899b70af5f748baab47eae940a55601