Subscriptions: Fix no enabled pairs for one asset (#1792)

If one asset is enabled but has no enabled pairs, we should ignore that
asset, even for non-pair related subscriptions.
That matches the existing code, but wasn't happening in the context of
asset.All subscriptions with just one asset in this state.
If a user wanted to have non-pair subscriptions, they should use
asset.Empty. Would expect other breakages with no pairs enabled, too.

Note: No enabled pairs for an enabled asset is a transient issue which
can occur due to enableOnePair racing against no available pairs. The
second run, available pairs would be populated and enableOnePair would
work. This situation could persist due to running with --dry or
containerised, though.

Fixes:
`
Okx websocket: subscription failure, myOrders all : subscription template did not generate the expected number of pair records for spread: Got 1;
Expected 0
`

Relates to #1420

exchanges/subscription/testdata/errors.tmpl

@@ -10,7 +10,6 @@
 	{{/* Incorrect number of pair entries */}}
 	{{- .PairSeparator -}}
 	{{- .PairSeparator -}}
-	{{- .PairSeparator -}}
 {{- else if eq .S.Channel "error4" }}
 	{{/* Too many BatchSize commands */}}
 	{{- range $asset, $pairs := $.AssetPairs }}

exchanges/subscription/testdata/subscriptions.tmpl

@@ -27,7 +27,7 @@
 	{{- range $asset, $pairs := $.AssetPairs }}
         {{- if eq $asset.String "spot" }}
             {{- range $batch := batch $pairs 3 -}}
-                {{ assetName $asset }}-{{ $batch.Join -}} -batching
+                {{ assetName $asset }}-{{ $batch -}} -batching
                 {{- $.PairSeparator -}}
             {{- end -}}
             {{- $.BatchSize -}} 3