fix: handle force_flush for rake task with arguments

[TeamNautilus]

This PR fixes an issue where force_flush was not correctly triggered when executing a Rake task with arguments. Previously, ::Rake.application.top_level_tasks stored task names including arguments (e.g., "task_name[arg]"), while the comparison in force_flush was done against name (which did not include arguments). This caused force_flush to be skipped for tasks with arguments.

Changes in this PR

• Updated force_flush logic to strip arguments from top_level_tasks before comparison.
• Modified tests to cover cases where a Rake task has arguments.
• Ensured force_flush is correctly called when a task with arguments is invoked.

[linux-foundation-easycla]

• ❌ - login: @TeamNautilus / name: Team Nautilus . The commit (6e4d750) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[kaylareopelle]

👋 Hi @TeamNautilus! Thanks for opening this PR! Would you mind signing the CLA?

[github-actions]

👋 This pull request has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this pull request will be closed eventually by the stale bot

[github-actions]

👋 This pull request has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this pull request will be closed eventually by the stale bot