fix(tasks): reindex users after IP cleanup

[Samk13]

❤️ Thank you for your contribution!

Description

As requested:

• Update login IP cleanup to process expired records in batches and bump affected user versions.
• Mark changed users through the datastore so search indexes stay in sync after IP removal.
• Cover version updates and datastore change tracking in the IP cleanup task test.

For an easier review, here is how to test the changes:

1. Seed DB values: see here
   uv run invenio shell scripts/dev/user-check-tools/seed_users_login_info.py

2. Rebuild user index so DB and OpenSearch start aligned: see here
   uv run invenio shell scripts/indices-migration-v13-14/user-groups-indices-migration.py

3. Check baseline: see here
   uv run invenio shell scripts/dev/user-check-tools/check_users_login_info_index.py

Run the task with invenio shell

from invenio_accounts.tasks import delete_ips
delete_ips()

run step 3 again and check the difference, or check with curl:

curl --location --request GET 'http://localhost:9200/latest-build-users-user-v3.0.0-*/_search' \
--header 'Content-Type: application/json' \
--data '{
    "_source": ["_index", "_id", "email_hidden", "last_login_ip", "current_login_ip", "current_login_at","last_login_ip"]
}' | jq

Check the screenshot before and after running the script to see the number of users in db and indices should match.

Before and after running the task:

Before

After

Note: This PR includes AI-assisted contributions that have been reviewed, refined, and validated manually.

Checklist

Ticks in all boxes and 🟢 on all GitHub actions status checks are required to merge:

• I'm aware of the code of conduct.
• I've created logical separate commits and followed the commit message format.
• I've added relevant test cases.
• I've added relevant documentation.
• I've marked translation strings.
• I've identified the copyright holder(s) and updated copyright headers for touched files (>15 lines contributions).
• I've NOT included third-party code (copy/pasted source code or new dependencies).
  • If you have added third-party code (copy/pasted or new dependencies), please reach out to an architect on Discord.

Frontend

• I've followed the CSS/JS and React guidelines.
• I've followed the web accessibility guidelines.
• I've followed the user interface guidelines.

Reminder

By using GitHub, you have already agreed to the GitHub’s Terms of Service including that:

1. You license your contribution under the same terms as the current repository’s license.
2. You agree that you have the right to license your contribution under the current repository’s license.

[Samk13]

I added the version_id bump because mark_changed() alone scheduled the reindex, but did not reliably replace the indexed user document.

My main concern is concurrent user updates while this task runs, since bumping version_id can trigger optimistic-lock conflicts for in-flight ORM updates.

If ther's a better way to force user reindexing without touching User.version_id, I'm happy to adjust.