temp: fix entitlements_to_expire should be capped at entitlements_count

[pshiu]

Description

On running Celery task expire_and_create_entitlements, for 6 entitlements to expire we get 100 batches:

15:58:48 2023-06-26 15:59:19,674 INFO 20101 [common.djangoapps.entitlements.management.commands.expire_and_create_entitlements] [user None] [ip None] expire_and_create_entitlements.py:86 - Total entitlements that have reached expiration period are 6 
15:58:48 2023-06-26 15:59:19,678 INFO 20101 [common.djangoapps.entitlements.management.commands.expire_and_create_entitlements] [user None] [ip None] expire_and_create_entitlements.py:95 - Found 100 batches. To enqueue entitlement expiration tasks, pass the -c or --commit flags.]

Cap the number of entitlements to expire to the total number of entitlements.

Additional Information

• Jira: REV-3574
• This PR is a fix forward for:
  • temp: added standard logging and removed celery logging #32577
  • temp: save results & add tests/fixes for expire_and_create_entitlements #32568
  • temp: fix use len(list) not list.count() in expire_and_create_entitlements #32565
  • temp: fix EncodeError for username in expire_and_create_entitlements #32564
  • temp: fix EncodeError & correct EntitlementSupportDetail action name in expire_and_create_entitlements #32562
  • temp: [REV-3574] create management command expire_and_create_entitlements #32528

[zubair-ce07]

On line 103, we will not need entitlement_count I guess. Can we remove that as well ?

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.