Support Version Wildcards

Being able to override all versions of a particular package is useful, especially ones with many, many version (think [firebase](https://www.npmjs.com/package/firebase))

The current format (to my understanding) requires that versions be explicitly declared to provide an override, like the following [example](https://github.com/clearlydefined/curated-data/blob/master/curations/npm/npmjs/%40azure/communication-calling.yaml):
```
coordinates:
name: communication-calling
namespace: '@azure'
provider: npmjs
type: npm
revisions:
1.0.0:
licensed:
declared: OTHER
1.0.0-beta.1:
licensed:
declared: OTHER
1.0.1-beta.1:
licensed:
declared: OTHER
1.1.0:
licensed:
declared: OTHER
1.1.0-beta.1:
licensed:
declared: OTHER
1.1.0-beta.2:
licensed:
declared: OTHER
1.2.0-beta.1:
licensed:
declared: OTHER
1.2.1-beta.1:
licensed:
declared: OTHER
1.2.2-beta.1:
licensed:
declared: OTHER
1.2.3-beta.1:
licensed:
declared: OTHER
1.3.2:
licensed:
declared: OTHER
1.3.2-beta.1:
licensed:
declared: OTHER
1.4.1-beta.1:
licensed:
declared: OTHER
1.4.3-beta.1:
licensed:
declared: OTHER
1.4.4:
licensed:
declared: OTHER
1.5.4:
licensed:
declared: OTHER
1.5.4-beta.1:
licensed:
declared: OTHER
1.6.1-beta.1:
licensed:
declared: OTHER
1.6.3:
licensed:
declared: OTHER
```

If we introduce version wildcards we can simply this list down to 1 entry

```yaml
coordinates:
name: communication-calling
namespace: '@azure'
provider: npmjs
type: npm
revisions:
1.*:
licensed:
declared: OTHER
```

Additionally, if the license does change in `2.0.0` this override list won't affect it