chore(EtsyTests): apply workaround into PostConfigure test

User side Post configure is later than provider side post configure. this causes the Scope not to be evaluated and the Mappings are not applyed automatically
HACK: add them all manually for the test postConfigure until decision is made this could be put in validate override or always consumer side?

Author: DevTKSS

test/AspNet.Security.OAuth.Providers.Tests/Etsy/EtsyTests.cs

@@ -60,7 +60,17 @@ void ConfigureServices(IServiceCollection services) => services.PostConfigureAll
         {
             o.IncludeDetailedUserInfo = true;
 
-            // User to include image claim
+            // Ensure the required scope is present before Validate() executes.
+            // BUG: This should not be necessary as the post-configure should add it. Assuming test Arrange should simulate eventual user setup.
+            if (!o.Scope.Contains(Scopes.EmailRead))
+            {
+                o.Scope.Add(Scopes.EmailRead);
+                o.ClaimActions.MapJsonKey(ClaimTypes.Email, "primary_email");
+                o.ClaimActions.MapJsonKey(ClaimTypes.GivenName, "first_name");
+                o.ClaimActions.MapJsonKey(ClaimTypes.Surname, "last_name");
+            }
+
+            // Opt-in to include image claim (not auto-mapped by provider to reduce payload size)
             o.ClaimActions.MapImageClaim();
         });