Remove workaround for mosaic client updates

The manual listener for `filterBy` changes is no longer needed with the
latest mosaic. The coordinator now properly handles `Selection` updates
and triggers query/queryResult calls when filterBy is updated.

Author: manzt

lib/clients/ValueCounts.ts

@@ -43,28 +43,6 @@ export class ValueCounts extends MosaicClient {
 		this.#table = options.table;
 		this.#column = options.field.name;
 		this.#field = options.field;
-
-		// FIXME: There is some issue with the mosaic client or the query we
-		// are using here. Updates to the Selection (`filterBy`) seem to be
-		// missed by the coordinator, and query/queryResult are not called
-		// by the coordinator when the filterBy is updated.
-		//
-		// Here we manually listen for the changes to filterBy and update this
-		// client internally. It _should_ go through the coordinator.
-		options.filterBy.addEventListener("value", async () => {
-			if (!this.#plot || !this.coordinator) {
-				return;
-			}
-			let filters = options.filterBy.predicate(this);
-			assert(
-				isExprNodeArray(filters),
-				`Filter is not expression array: ${filters}`,
-			);
-			let query = this.query(filters);
-			let data = await this.coordinator.query(query);
-			assert(isFlechetteTable(data), "Expected a flechette table.");
-			this.#plot.data.value = data;
-		});
 	}
 
 	override query(filter: Array<ExprNode> = []): Query {