Update sytests, add /capabilities endpoint into CS API

clientapi/routing/routing.go

@@ -551,4 +551,10 @@ func Setup(
 			return DeleteTag(req, accountDB, device, vars["userId"], vars["roomId"], vars["tag"], syncProducer)
 		}),
 	).Methods(http.MethodDelete, http.MethodOptions)
+
+	r0mux.Handle("/capabilities",
+		common.MakeAuthAPI("capabilities", authData, func(req *http.Request, device *authtypes.Device) util.JSONResponse {
+			return GetCapabilities(req, queryAPI)
+		}),
+	).Methods(http.MethodGet)
 }

sytest-blacklist

@@ -19,3 +19,6 @@ Alias creators can delete alias with no ops
 # Blacklisted because matrix-org/dendrite#847 might have broken it but we're not
 # really sure and we need it pretty badly anyway
 Real non-joined users can get individual state for world_readable rooms after leaving
+
+# Blacklisted until matrix-org/dendrite#862 is reverted due to Riot bug
+Latest account data appears in v2 /sync

sytest-whitelist

@@ -112,7 +112,7 @@ User can invite local user to room with version 4
 Should reject keys claiming to belong to a different user
 Can add account data
 Can add account data to room
-Latest account data appears in v2 /sync
+#Latest account data appears in v2 /sync
 New account data appears in incremental v2 /sync
 Checking local federation server
 Inbound federation can query profile data
@@ -227,3 +227,5 @@ Guest users can sync from world_readable guest_access rooms if joined
 Guest users can sync from default guest_access rooms if joined
 Real non-joined users cannot room initalSync for non-world_readable rooms
 Push rules come down in an initial /sync
+Regular users can add and delete aliases in the default room configuration
+Regular users can add and delete aliases when m.room.aliases is restricted