feat(logging-controller): Add expiration to logs

[FrederikBolding]

Explanation

Add expiryTime constructor argument to LoggingController, it defaults to 7 days.

When adding a new log entry, we iterate through the existing logs and discard any that were logged before the expiry cutoff.

Additionally simplifies the controller by using UUID v4, not checking for conflicts and removing an unused dependency on controller-utils.

References

N/A

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
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

Medium Risk
Changes persisted log retention by auto-deleting old entries on add, which can remove historical support/debug data. Scope is limited to LoggingController and the new constructor option is backward-compatible.

Overview
Adds an optional expiryTime constructor argument to LoggingController (default 7 days). On each add, expired entries are removed before the new log is stored, so persisted logs no longer grow indefinitely.

Also simplifies ID generation by switching from UUID v1 with collision retries to UUID v4, and drops the unused @metamask/controller-utils dependency in favor of @metamask/utils for duration helpers.

^{Reviewed by Cursor Bugbot for commit 5e0a54e. Bugbot is set up for automated code reviews on this repo. Configure here.}

[GuillaumeRx]

What about also doing it when we initialize the controller ?

[FrederikBolding]

Yeah, we could

[FrederikBolding]

Though it probably doesn't matter much as I think we wouldn't persist until an actual change happens 🤔 WDYT?

[GuillaumeRx]

Yes that makes sense !