1. Modify the wm/core/switch/${id}/flow/json's return format, it use a
array to shows the flow entries, e.g. I think this format is more convenience for restapi caller.

"flows": [
        {
            "byte_count": "2498",
            "cookie": "0",
            "duration_sec": "4",
            "flags": "0",
            "hard_timeout_sec": "0",
            "idle_timeout_sec": "0",
            "instructions": {
                "apply_actions": {
                    "output": "-3"
                }
            },
            "match": {},
            "packet_count": "33",
            "priority": "32768",
            "table_id": "0",
            "version": "OF_13"
        },
        {
            "byte_count": "0",
            "cookie": "9007199254740992",
            "duration_sec": "2",
            "flags": "0",
            "hard_timeout_sec": "0",
            "idle_timeout_sec": "5",
            "instructions": {
                "apply_actions": {
                    "output": "1"
                }
            },
            "match": {
                "dl_dst": "e6:85:22:16:59:87",
                "dl_src": "b2:ac:81:4a:92:57",
                "dl_type": "2054",
                "ingress_port": "2"
            },
            "packet_count": "0",
            "priority": "0",
            "table_id": "0",
            "version": "OF_13"
        },
2. Adding the new coloum write_actions and replace the original action field to apply_actions.
3. Since the OF1.1+ use the OXM format to present the match filed, we don't need to use the wildcard to check what kind of the fild be used in the flow, we can directly use the query result. If we want to make it compatible with OF1.0, we need to use the version field to check in the javascript and modify the way how we get the match rules.
4. It has only been test with the default forwarding module and the flow entries looks right. It need to be tested with other match rule and actions.
5. replace the tab with 4-spaces