Minor bug fix for exiting early when identifying requestGraph in loadGraphs

[irismoini]

↪️ Pull Request

The loadGraph function sorts the files in the cache by size and modification time and then iterates through these files to identify the requestGraph. Because the requestGraph is written to the cache with the setLargeBlob function, the file name always ends with '-0'. There's no need to waste time deserializing files that don't end with '-0' and checking to see if they are the requestGraph. However, there's currently a bug in this early stopping condition when identifying the requestGraph. This PR fixes that.

💻 Examples

🚨 Test instructions

Commented out the break condition and logged the files that could possibly being deserialized if the requestGraph wasn't found on the first try. Previously files that did not end with '-0' where being deserialized, now only files ending with '-0' will be.

✔️ PR Todo

• Added/updated unit tests for this change
• Filled out test instructions (In case there aren't any unit tests)
• Included links to related issues/PRs