e2e: exercise the report endpoint in tracker resource test

The previous test seeded tracker resources directly via the
GraphQL `CreateTrackerResource` mutation, which doesn't go
through the public `/report` handler. Switching the seeding to
`ReportDetectedResources` covers the end-to-end path -- payload
decoding, validation, and the new upsert -- so the listing assert
is now grounded in the same write path that real clients use.

Signed-off-by: Émile Ré <emile@getprobo.com>

e2e/console/tracker_resource_test.go

@@ -105,9 +105,7 @@ func TestTrackerResource_List(t *testing.T) {
 		owner := testutil.NewClient(t, testutil.RoleOwner)
 
 		bannerID := factory.CreateCookieBanner(owner)
-		categoryID := factory.CreateCookieCategory(owner, bannerID)
-		factory.CreateTrackerResource(owner, categoryID)
-		factory.CreateTrackerResource(owner, categoryID)
+		factory.ReportDetectedResources(owner, bannerID, 2)
 
 		const query = `
 			query($id: ID!) {