fix: Remove type filter from relations that breaks prod use case

• fix: Remove type filter from relations that breaks prod use case

In production, the WGCR relation is in a different group than the other relations. As we already filter out the unneeded data, we're safe to just remove the filter, as the relations data isn't a large data set. This happened due to a bug fix that revealed the weirdness between the relations

src/main/java/org/eclipsefoundation/wg/api/FoundationDbAPI.java

@@ -39,13 +39,12 @@ public interface FoundationDbAPI {
    * Fetches all system relations filtered by the given type.
    * 
    * @param baseParams Base request paramters used for pagination.
-   * @param type The given relation type filter.
    * @return A Response containing the filtered relations
    */
   @GET
   @Compressed
   @Path("/sys/relations")
-  RestResponse<List<SysRelationData>> getRelations(@BeanParam BaseAPIParameters baseParams, @QueryParam("type") String type);
+  RestResponse<List<SysRelationData>> getRelations(@BeanParam BaseAPIParameters baseParams);
 
   /**
    * Fetches all Full org contacts containing Person, Org, and SysRelation entities. Filtered by document ids.