Incorrect pipeline total element count for `bst track`

When running bst track without --deps all, the pipeline status area still shows a total element count inclusive of the track target's elements, even though the intention (and behavior) is only to track a single element.

This may also be true in other scenarios like with bst fetch, the counter should be changed to be based on the real list of elements which are queued for scheduling.