fix: prevent PhishingController invalid API requests with -Infinity timestamp

[cryptodev-2s]

Explanation

This PR fixes an edge case in the PhishingController where empty phishingLists would trigger API requests with an invalid -Infinity timestamp.

When the phishingLists array is empty and #updateHotlist() is called, the code attempts to get the maximum timestamp using Math.max(...this.state.phishingLists.map(({ lastUpdated }) => lastUpdated)). With an empty array, this results in -Infinity, causing invalid API requests to /v1/diffsSince/-Infinity.

Added an early return check in #updateHotlist() when phishingLists is empty to prevent making the invalid API request.

References

Fixes #4194

Changelog

Check Changelog

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 highlighted breaking changes using the "BREAKING" category above as appropriate
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

[mcmire]

Do we want a test for this to ensure that this doesn't cause a problem again?