RoleManager.RoleExistsAsync role name normalization issue

[faresamr]

PR Title
RoleManager.RoleExistsAsync role name normalization issue

PR Description
As described in the linked issue, role name gets normalized twice

• Remove unnecessary normalization in RoleExistsAsync, since the value will be passed to FindByNameAsync and the normalization will be handled there.
• Update the unit test by inject a custom normalizer which returns different value in case recursive calls
  Normalize(Normalize("foo")) != Normalize("foo") to cover this case in both RoleManager and UserManager.
• Stabilizing both RoleManager and UserManager unit tests to cope with the new normalizer.

Fixes #35946

[dnfadmin]

All CLA requirements met.

[faresamr]

There are 3 checks failed one of them required and I'm assuming that this is not expected, the three of them failed for the same reason "a file can not be accessed because it's being used by another process"
How can I rerun these checks?

[TanayParikh]

How can I rerun these checks?

We're having some file contention issues in the CI. I triggered the failed tests to re-run.

[HaoK]

Thanks, for doing this so quickly @faresamr !

[HaoK]

/backport to release/6.0

[github-actions]

Started backporting to release/6.0: https://github.com/dotnet/aspnetcore/actions/runs/1191548482

[aarindam10]

I am using 6.0 version, _roleManager.RoleExistsAsync is still not working! throwing TaskCanceledException with message "A task was canceled in Microsoft.EntityFrameworkCore.Relational", but earlier thread about "roleManager.RoleExistsAsync not working" - is marked as closed by [msftbot] bot.

[ghost]

Hi @aarindam10. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.

[aarindam10]

Hi @aarindam10. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.

Yes, I could open an new issue, but I am trying to post on same thread, so people who contributed on this issue, will know what’s going in new version of Identity 6

[ghost]

Hi @aarindam10. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.

[aarindam10]

await _roleManager.CreateAsync(role) throws error, but following code executed successfully.

_roleManager.CreateAsync(role).GetAwaiter().GetResult()

Though the work is carried out, but not convinced why the first line of code is throwing error? not happy! will be waiting for right solution.

[ghost]

Hi @aarindam10. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.