trade: extend "Lines Report" to allow filtering by use

Nowadays instead of creating many portal types, we use `use` category to
separate different types of movements, so it makes sense to filter by use,
the same way that we already were able to filter by portal type.
2 jobs for feat/lines_report_use
in 0 seconds, using 0 compute credits, and was queued for 1 second