Fixes#1737 - Setting the schedma-id as the pid (parent-id) for the

sequences node instead of the server-id.

Due to this - during updating the sequence node, it was not able to find
out the correct parent node, and it was updating the existing node, but
- later it (considering the old node) was removed by the replace logic.

web/pgadmin/browser/server_groups/servers/databases/schemas/sequences/__init__.py

@@ -210,19 +210,18 @@ class SequenceView(PGChildNodeView):
             return make_json_response(
                 data=self.blueprint.generate_browser_node(
                     row['oid'],
-                    sid,
+                    scid,
                     row['name'],
                     icon="icon-%s" % self.node_type
                 ),
                 status=200
             )
 
-
         for row in rset['rows']:
             res.append(
                 self.blueprint.generate_browser_node(
                     row['oid'],
-                    sid,
+                    scid,
                     row['name'],
                     icon="icon-%s" % self.node_type
                 ))