Gives up after first failure of use-recent-api-version with each resource type

```json
{
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"parameters": {},
"functions": [],
"resources": [
{
"name": "res1",
"type": "Microsoft.VSOnline/registeredSubscriptions",
"apiVersion": "2020-05-26-privatepreview"
},
{
"name": "res2",
"type": "Microsoft.VSOnline/registeredSubscriptions",
"apiVersion": "2020-05-26-preview"
},
{
"name": "res3",
"type": "Microsoft.VSOnline/registeredSubscriptions",
"apiVersion": "2020-05-26-beta"
},
{
"name": "res4",
"type": "Microsoft.VSOnline/registeredSubscriptions",
"apiVersion": "2020-05-26-alpha"
},
{
"name": "res5",
"type": "Microsoft.VSOnline/registeredSubscriptions",
"apiVersion": "2019-07-01-privatepreview"
},
{
"name": "res6",
"type": "Microsoft.VSOnline/registeredSubscriptions",
"apiVersion": "2019-07-01-preview"
},
{
"name": "res7",
"type": "Microsoft.VSOnline/registeredSubscriptions",
"apiVersion": "2019-07-01-beta"
},
{
"name": "res8",
"type": "Microsoft.VSOnline/registeredSubscriptions",
"apiVersion": "2019-07-01-alpha"
}

],
"outputs": {}
}

```
Actual:
```
apiVersions Should Be Recent
[-] apiVersions Should Be Recent (94 ms)
Api versions must be the latest or under 2 years old (730 days) - API version 2020-05-26-preview of Microsoft.VSOnline/registeredSubscriptions is 772 days old Line: 15, Column: 14
Valid Api Versions:
2020-05-26-beta
2020-05-26-privatepreview
```
Expected: multiple errors

Start with the use-recent-api-version check represented by the “apiVersions Should Be Recent” output and reproduce it with the supplied deployment template. Verify that each old API version for the resource type is reported rather than stopping after the first failure; done means the example produces multiple errors.

Written by the indexing model from the issue text.