Release/1001.0.0 (#8900)

## Explanation

<!--
Thanks for your contribution! Take a moment to answer these questions so
that reviewers have the information they need to properly understand
your changes:

* What is the current state of things and why does it need to change?
* What is the solution your changes offer and how does it work?
* Are there any changes whose purpose might not obvious to those
unfamiliar with the domain?
* If your primary goal was to update one package but you found you had
to update another one along the way, why did you do so?
* If you had to upgrade a dependency, why did you do so?
-->

This PR releases `@metamask/compliance-controller` `2.1.1`.
`2.1.0` release metadata was already merged to `main`, but that PR did
not use the release PR title format, so the publish flow was not
triggered and `@metamask/compliance-controller@2.1.0` was not tagged or
published.

Because `main` already contains version `2.1.0`, this PR intentionally
bumps the package to `2.1.1` so the release tooling can detect a package
version change and publish the compliance-controller changes normally.

Relative to the last published package version, this release includes:

- Support for configuring `ComplianceService` with an explicit
Compliance API URL.
- A new `selectAreAnyWalletsBlocked` selector.
- Case-insensitive cached compliance lookups for valid EVM addresses.

This PR does not introduce new runtime behavior beyond the
compliance-controller changes already merged to `main`; it corrects the
release metadata so those changes can be published.

## References

<!--
Are there any issues that this pull request is tied to?
Are there other links that reviewers should consult to understand these
changes better?
Are there client or consumer pull requests to adopt any breaking
changes?

For example:

* Fixes #12345
* Related to #67890
-->

## Checklist

- [ ] I've updated the test suite for new or updated code as appropriate
- [ ] I've updated documentation (JSDoc, Markdown, etc.) for new or
updated code as appropriate
- [ ] I've communicated my changes to consumers by [updating changelogs
for packages I've
changed](https://github.com/MetaMask/core/tree/main/docs/processes/updating-changelogs.md)
- [ ] I've introduced [breaking
changes](https://github.com/MetaMask/core/tree/main/docs/processes/breaking-changes.md)
in this PR and have prepared draft pull requests for clients and
consumer packages to resolve them

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Only version and changelog metadata change; compliance runtime
behavior is untouched in this diff.
> 
> **Overview**
> This PR is a **release-only** update for
`@metamask/compliance-controller`: it bumps the published version from
**2.1.0** to **2.1.1** in `package.json` and aligns `CHANGELOG.md`
(section title, compare links, and the `[Unreleased]` anchor).
> 
> The only substantive changelog text change is a wording tweak under
**Fixed**: cached wallet compliance lookups are described as matching
**valid** EVM addresses case-insensitively (previously “EVM addresses”
without “valid”). No controller, service, or test code is modified in
the diff.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
2ae49f6. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

Author: geositta

packages/compliance-controller/CHANGELOG.md

@@ -7,7 +7,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
-## [2.1.0]
+## [2.1.1]
 
 ### Added
 
@@ -20,7 +20,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Fixed
 
-- Match EVM addresses case-insensitively when reading cached wallet compliance statuses ([#8820](https://github.com/MetaMask/core/pull/8820)).
+- Match valid EVM addresses case-insensitively when reading cached wallet compliance statuses ([#8820](https://github.com/MetaMask/core/pull/8820)).
 
 ## [2.0.1]
 
@@ -71,8 +71,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - Bump `@metamask/controller-utils` from `^11.18.0` to `^11.19.0` ([#7995](https://github.com/MetaMask/core/pull/7995))
 
-[Unreleased]: https://github.com/MetaMask/core/compare/@metamask/compliance-controller@2.1.0...HEAD
-[2.1.0]: https://github.com/MetaMask/core/compare/@metamask/compliance-controller@2.0.1...@metamask/compliance-controller@2.1.0
+[Unreleased]: https://github.com/MetaMask/core/compare/@metamask/compliance-controller@2.1.1...HEAD
+[2.1.1]: https://github.com/MetaMask/core/compare/@metamask/compliance-controller@2.0.1...@metamask/compliance-controller@2.1.1
 [2.0.1]: https://github.com/MetaMask/core/compare/@metamask/compliance-controller@2.0.0...@metamask/compliance-controller@2.0.1
 [2.0.0]: https://github.com/MetaMask/core/compare/@metamask/compliance-controller@1.0.2...@metamask/compliance-controller@2.0.0
 [1.0.2]: https://github.com/MetaMask/core/compare/@metamask/compliance-controller@1.0.1...@metamask/compliance-controller@1.0.2

packages/compliance-controller/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@metamask/compliance-controller",
-  "version": "2.1.0",
+  "version": "2.1.1",
   "description": "Manages OFAC compliance checks for wallet addresses",
   "keywords": [
     "Ethereum",