Add license lint check

### What is this about?

We want all of our dependencies to have licenses that are compatible with how we are using them, and compatible with the terms of our license.

We should add a lint check to ensure new packages meet these criteria. For existing packages with licences that don't meet these criteria, we can exclude them from this status check for now and document them as bugs to address separately.

### Scenario

_No response_

### Design

_No response_

### Technical Details

[Apply same solution to extension](https://github.com/MetaMask/metamask-extension/issues/28326)

### Threat Modeling Framework

_No response_

### Acceptance Criteria

_No response_

### Stakeholder review needed before the work gets merged

- [X] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [X] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)

### References

_No response_

Start by reviewing the linked MetaMask extension issue 28326 and the repository's existing lint and status-check setup. Determine how dependency licenses are evaluated, which existing packages need temporary exclusions, and how those exceptions should be documented. Done means a repeatable check covers new packages while preserving documented exceptions for existing issues.

Written by the indexing model from the issue text.