Exempt pyparsing from license check

[TheJulianJES]

Proposed change

This adds pyparsing to the list of license exceptions, as they changed their license identifier in the latest version to something we aren't detecting. It's likely something that should be fixed on their side at some point. For now, we should work around it to unblock CI on dev.

• pyparsing license identifier change commit: pyparsing/pyparsing@085fa0d
• Failed run: https://github.com/home-assistant/core/actions/runs/20438183016/job/58724756375
• LICENSE file: https://github.com/pyparsing/pyparsing/blob/master/LICENSE, also note the recently added author copyright at the top

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[TheJulianJES]

Cache version needs to be bumped as well. Will do in a second.

[Copilot]

Pull request overview

This PR adds pyparsing to the license check exceptions list to unblock CI on the dev branch. The pyparsing library recently changed its license identifier format, which the automated license detection system no longer recognizes, even though it remains an MIT-licensed package.

Key changes:

• Added "pyparsing" entry to the EXCEPTIONS set with a comment indicating it uses MIT license

[Copilot]

The comment should provide more context about why pyparsing is in the exceptions list. Consider adding a reference to the upstream commit that changed the license identifier or a note explaining that the license identifier format is not being detected correctly. For example: "# MIT - license identifier format not detected (pyparsing/pyparsing@085fa0d)" This would help future maintainers understand why this exception exists and when it might be safe to remove.

Suggested change

	"pyparsing", # MIT
	"pyparsing", # MIT - license identifier format not detected (pyparsing/pyparsing@085fa0d)