chore: cleanup changelog uncategorized sections (#7136)

## 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 cleans up uncategorized sections from three changelog files by
removing redundant entries.

### Changes

- Removed uncategorized section from `bridge-controller` changelog
- Removed uncategorized section from `bridge-status-controller`
changelog
- Removed uncategorized section from `claims-controller` changelog

### Motivation

The uncategorized sections contained internal release management entries
(Release/671.0.0) and general maintenance items (ESLint auto-fixes) that
don't provide value to consumers of these packages. Removing these
entries keeps the changelogs focused on meaningful changes.

## 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/contributing.md#updating-changelogs),
highlighting breaking changes as necessary
- [ ] I've prepared draft pull requests for clients and consumer
packages to resolve any breaking changes

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Removes redundant "Uncategorized" sections from three package
changelogs to keep entries focused on meaningful changes.
> 
> - **Changelogs**:
> - `packages/bridge-controller/CHANGELOG.md`: remove `Uncategorized`
section (internal release/ESLint entries).
> - `packages/bridge-status-controller/CHANGELOG.md`: remove
`Uncategorized` section (internal release entry).
> - `packages/claims-controller/CHANGELOG.md`: remove `Uncategorized`
section (CI/tsconfig entry).
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
949d3b9. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

Author: cryptodev-2s

packages/bridge-controller/CHANGELOG.md

@@ -9,11 +9,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [60.1.0]
 
-### Uncategorized
-
-- Release/671.0.0 ([#7126](https://github.com/MetaMask/core/pull/7126))
-- chore: Fix all auto-fixable ESLint warnings ([#7105](https://github.com/MetaMask/core/pull/7105))
-
 ### Added
 
 - Added support for bridging and swapping tokens on the Tron blockchain ([#6862](https://github.com/MetaMask/core/pull/6862))

packages/bridge-status-controller/CHANGELOG.md

@@ -9,10 +9,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [60.1.0]
 
-### Uncategorized
-
-- Release/671.0.0 ([#7126](https://github.com/MetaMask/core/pull/7126))
-
 ### Added
 
 - Added support for bridging and swapping tokens on the Tron blockchain ([#6862](https://github.com/MetaMask/core/pull/6862))

packages/claims-controller/CHANGELOG.md

@@ -9,10 +9,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [0.2.0]
 
-### Uncategorized
-
-- ci: Fix `claims-controller` errors in `tsconfig.json` ([#7092](https://github.com/MetaMask/core/pull/7092))
-
 ### Added
 
 - Added new public method, `fetchClaimsConfigurations` to fetch the claims configuration from the Claims backend. ([#7109](https://github.com/MetaMask/core/pull/7109))