engine/ Improve Readability and Maintainability of Data Purge Function (purge())

[itstanany]

IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).

Fixes #2528

Description

Refactor purge() function for improved readability and maintainability

This pull request refactors the purge function to enhance code clarity and maintainability. The current implementation utilizes nested conditionals for resource presence, local changes, and force purge checks. This refactoring separates these concerns for improved readability.

Changes:

• Combined Local Changes and Force Purge Check: Combines the checks for local changes (localChanges.isNotEmpty()) and the forcePurge flag within a single condition.
• Concise Comments: Adds concise comments to explain the logic behind each step.
• Reduced Redundancy:

These improvements promote better code understanding and maintainability for future developers.

Alternative(s) considered
Have you considered any alternatives? And if so, why have you chosen the approach in this PR?

Type
Choose one: Code health

Screenshots (if applicable)

Checklist

• I have read and acknowledged the Code of conduct.
• I have read the Contributing page.
• I have signed the Google Individual CLA, or I am covered by my company's Corporate CLA.
• I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach.
• I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the style guide of this project.
• I have run ./gradlew check and ./gradlew connectedCheck to test my changes locally.
• I have built and run the demo app(s) to verify my change fixes the issue and/or does not break the demo app(s).

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[MJ1998]

LGTM