Fix total_impact filter

The problem is the way the query method works internally.

It constructs an AR entity from the query request to allow filtering by specific fields.

When an "empty" AR entity is created for the query request it also calculates the `total_impact` (the log entry you saw) which results to `1`, and then only filters for AR that have a total_impact of 1, which is what you saw in the activityrecord.list result.

By setting total_impact to `none` when no values are available it isn't added to the filter and all AR are displayed. I checked against our datastore and activity_title seems to be the best field to check since it's never null (only an empty string for some activities).