[BUG] Share expiration tasks fails when share is already revoked and has expiration

[TejasRGitHub]

Describe the bug

When running share expiration task, all active shares with expiration are pulled in along with the share item

The current logic of updating the share item status puts all the share items in revoke_approved state and then revokes the share. While fetching the share items it only pull in the 'Share_Succeeded' state and then makes the transition

There is a bug in which if a share has all the share items in revoke succeeded state and then if the share also has an expiration date, then it calls the revoke_share function which results in the following error

An error occurred (UnauthorizedOperation) when calling RevokeItems operation: This transition is not possible, Revoke_Succeeded cannot go to ['Revoke_Approved']. If there is a sharing or revoking in progress wait until it is complete and try again. For share extensions delete unused items and try again

How to Reproduce

*P.S. Please do not attach files as it's considered a security risk. Add code snippets directly in the message body as much as possible.*

Create a share with expiration ( by enabling expiration on dataset )
Let the share expired and then run the share expiration task
The expiration task should fail

Expected behavior

No response

Your project

No response

Screenshots

No response

OS

Mac

Python version

3.9

AWS data.all version

2.6

Additional context

No response