feat: Store deleted users in a table

[hangy]

What

• Store limited information about deleted users in a separate table

Part of

• feat: [WIP] Implement OIDC sign-in openfoodfacts-server#9251

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 47.22222% with 38 lines in your changes are missing coverage. Please review.

Project coverage is 42.50%. Comparing base (4cd963a) to head (9377817).

Files	Patch %	Lines
...ersistDeletedUserEventListenerProviderFactory.java	0.00%	28 Missing ⚠️
...odfacts/github/keycloak/jpa/DeletedUserEntity.java	79.31%	3 Missing and 3 partials ⚠️
...loak/events/RedisEventListenerProviderFactory.java	0.00%	4 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main      #14      +/-   ##
============================================
+ Coverage     40.96%   42.50%   +1.53%     
- Complexity       24       51      +27     
============================================
  Files            13       17       +4     
  Lines           249      320      +71     
  Branches         11       15       +4     
============================================
+ Hits            102      136      +34     
- Misses          138      172      +34     
- Partials          9       12       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[john-gom]

Looks good. Any reason why you added an extra event handler rather than putting the code in the existing one?

[hangy]

Any reason why you added an extra event handler rather than putting the code in the existing one?

In my mind, one issue is that they'll never be totally transactional. All of this happens as the account has been removed from the store already. I started with all of the code in one handler, but having to try..catch..log and continuing with the next (ie. Redis or JPA) didn't feel too good.