Consider EF ExecuteUpdate and SetProperty for our various cleanup processes about identityserver

[josephdecock]

In addition, we would also like to consider fuzzing the startup time of the cleanup job to mitigate the "thundering herd" issue, where all scaled instances start their job at once.

[josephdecock]

Docs for reference - https://learn.microsoft.com/en-us/ef/core/saving/execute-insert-update-delete

[bbartels]

I created this PR to use ExecuteDelete during frequently used persistedgrant operations #1427

[josephdecock]

Making this change probably can't be done at all for server side sessions, and might require a breaking change for token cleanup.

The session cleanup job needs to load the sessions it is cleaning up in order to do coordination (we can't send logout notifications when a session times out without loading the session to find out which clients to notify). There might be small optimizations possible, but the fundamental problem remains that we need to load the records as they are deleted.

The token cleanup job could be changed to use these APIs, but we would need to stop using the IOperationalStoreNotification. Currently, the token cleanup job sends all the records it deletes to that service, if one is registered. This is an optional dependency that I didn't even know we had, but it's been around for years now. Obviously if we change our cleanup to stop loading the records we're deleting, we can't send those records to the notification service, and this is a breaking change for anyone who implemented that interface.

Options:

1. Accept the breaking change
2. Maintain two versions of the cleanup service - one which is the same as we have today, and the other which doesn't send notifications because it is more optimized. We could make the optimized cleanup service be the default, but make the method that registers the notification switch to the legacy service
3. As a variation of option 2, we could put both code paths in the cleanup service, and switch between them based on if we have a registered notification service
4. Reject this idea and do nothing